Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e5f7b978b3e82418b9b3e70afdb610f5a9f416d6cf4269b69df92ea122f446

Tx prefix hash: 849f00feceb6eb23d475c76dcca70b4653ee2dabffa8b3139a60d20b35340059
Tx public key: 426016e03a6fe8c43fe338f7964faf1fd4cfefe8ca9ee9a808196d31bbe3fd9a
Timestamp: 1627367159 Timestamp [UCT]: 2021-07-27 06:25:59 Age [y:d:h:m:s]: 03:191:06:15:27
Block: 301834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908655 RingCT/type: yes/0
Extra: 01426016e03a6fe8c43fe338f7964faf1fd4cfefe8ca9ee9a808196d31bbe3fd9a0211000000112512b0af000000000000000000

1 output(s) for total of 61.361949449000 dcy

stealth address amount amount idx
00: 6383ba676292d74484a2f740ebdc9dc13ddf770a43566c77955fef21dc44bb8a 61.361949449000 630359 of 0

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": 301844, "vin": [ { "gen": { "height": 301834 } } ], "vout": [ { "amount": 61361949449, "target": { "key": "6383ba676292d74484a2f740ebdc9dc13ddf770a43566c77955fef21dc44bb8a" } } ], "extra": [ 1, 66, 96, 22, 224, 58, 111, 232, 196, 63, 227, 56, 247, 150, 79, 175, 31, 212, 207, 239, 232, 202, 158, 233, 168, 8, 25, 109, 49, 187, 227, 253, 154, 2, 17, 0, 0, 0, 17, 37, 18, 176, 175, 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