Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f0fb5673363763e9dc4cb4a52a8e6ef650526926401b270f2e13dc248aa776

Tx prefix hash: c287347d8b9840c4895dfcc2854f7c9df85a702d357fc8de9932676ebd50c08f
Tx public key: 5593304ffa643ae3a47d612b61b780b37c7ccee9cb803277a7bb54759b0f0855
Timestamp: 1704292445 Timestamp [UCT]: 2024-01-03 14:34:05 Age [y:d:h:m:s]: 01:027:15:08:35
Block: 927347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280806 RingCT/type: yes/0
Extra: 015593304ffa643ae3a47d612b61b780b37c7ccee9cb803277a7bb54759b0f085502110000000679bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b4bb24ac4f1fa93f5a77509c2d18ceaae721db3c31b666a1b749c43fce569f 0.600000000000 1385183 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": 927357, "vin": [ { "gen": { "height": 927347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b4bb24ac4f1fa93f5a77509c2d18ceaae721db3c31b666a1b749c43fce569f" } } ], "extra": [ 1, 85, 147, 48, 79, 250, 100, 58, 227, 164, 125, 97, 43, 97, 183, 128, 179, 124, 124, 206, 233, 203, 128, 50, 119, 167, 187, 84, 117, 155, 15, 8, 85, 2, 17, 0, 0, 0, 6, 121, 189, 163, 190, 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