Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30f1a9e5dbd0348078d5f275a642e0f67760bd7e11da00680f277e16b8765f86

Tx prefix hash: bebedd558ca537fbba540a5ae30e9430eefd29344fb279c51ed2e899f67f0366
Tx public key: c95ecb5b7c8e924be841794c952a86dd1fd1f3f62b4ce02db4cbaf8e2c3be23e
Timestamp: 1574522703 Timestamp [UCT]: 2019-11-23 15:25:03 Age [y:d:h:m:s]: 05:036:09:06:03
Block: 15652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1168984 RingCT/type: yes/0
Extra: 01c95ecb5b7c8e924be841794c952a86dd1fd1f3f62b4ce02db4cbaf8e2c3be23e021100000008354bbe3b000000000000000000

1 output(s) for total of 544.677342360000 dcy

stealth address amount amount idx
00: ce9fae59b710ac0b02f4d62f1b79c22b7575aa8ffc65c620013c8d5883e6a583 544.677342360000 21160 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": 15662, "vin": [ { "gen": { "height": 15652 } } ], "vout": [ { "amount": 544677342360, "target": { "key": "ce9fae59b710ac0b02f4d62f1b79c22b7575aa8ffc65c620013c8d5883e6a583" } } ], "extra": [ 1, 201, 94, 203, 91, 124, 142, 146, 75, 232, 65, 121, 76, 149, 42, 134, 221, 31, 209, 243, 246, 43, 76, 224, 45, 180, 203, 175, 142, 44, 59, 226, 62, 2, 17, 0, 0, 0, 8, 53, 75, 190, 59, 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