Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70b000e9a0a6a607a68b5dd35f12abffb60d8b73a558fecec4d60ee4b840981

Tx prefix hash: 706d0586b1b7c9d2a717348e70f862fe25d4c6159a8cdcb34cf79d791d6441ac
Tx public key: 63cc2dffd84e6b74b49eea6663d0507033810e6faa878c2b1ba2cf736c7f9e37
Timestamp: 1748961717 Timestamp [UCT]: 2025-06-03 14:41:57 Age [y:d:h:m:s]: 00:170:07:04:25
Block: 1297128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119383 RingCT/type: yes/0
Extra: 0163cc2dffd84e6b74b49eea6663d0507033810e6faa878c2b1ba2cf736c7f9e3702110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d79240cbccae545a106f6daf0c61052cbcb274450f316dc652568887cff8d01 0.600000000000 1784645 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": 1297138, "vin": [ { "gen": { "height": 1297128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d79240cbccae545a106f6daf0c61052cbcb274450f316dc652568887cff8d01" } } ], "extra": [ 1, 99, 204, 45, 255, 216, 78, 107, 116, 180, 158, 234, 102, 99, 208, 80, 112, 51, 129, 14, 111, 170, 135, 140, 43, 27, 162, 207, 115, 108, 127, 158, 55, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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