Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ccb7adfd49bcf8d285f016293d3ac9b467f845fd69499847859e3206378224d4

Tx prefix hash: 9fec4a99a3dc741445d2063a1ceb32bb2fc689fdd6ea2f2ba3adf8769dd162d2
Tx public key: 8a0e9ba9969f9624153efdfe1b67fafce27377408615ce5cd71dc098c74d90f5
Timestamp: 1722466586 Timestamp [UCT]: 2024-07-31 22:56:26 Age [y:d:h:m:s]: 00:175:23:21:32
Block: 1077998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125860 RingCT/type: yes/0
Extra: 018a0e9ba9969f9624153efdfe1b67fafce27377408615ce5cd71dc098c74d90f502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5a1bf51f225af08af4f9c55c127f2623a3ba2f0febfe05bf90635926f7b55d 0.600000000000 1550553 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1078008, "vin": [ { "gen": { "height": 1077998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5a1bf51f225af08af4f9c55c127f2623a3ba2f0febfe05bf90635926f7b55d" } } ], "extra": [ 1, 138, 14, 155, 169, 150, 159, 150, 36, 21, 62, 253, 254, 27, 103, 250, 252, 226, 115, 119, 64, 134, 21, 206, 92, 215, 29, 192, 152, 199, 77, 144, 245, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8