Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597c47b7174875e5170e768c4730f41b8d10a0626fd68943c3faf74a8161dfad

Tx prefix hash: 09deed3a8c1456b5e50b561b3439086bb69882d0e24c0d969f79cc398e7e7e84
Tx public key: a5b7161e72b5cd2fcf97968b4c144d7ed927fb31007fb9f3b1067885185e3505
Timestamp: 1749661490 Timestamp [UCT]: 2025-06-11 17:04:50 Age [y:d:h:m:s]: 00:152:11:38:04
Block: 1302892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106667 RingCT/type: yes/0
Extra: 01a5b7161e72b5cd2fcf97968b4c144d7ed927fb31007fb9f3b1067885185e35050211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f70b9acdd482017049affbf4cfedb1b095d6e786d5f33734f1aef6dc27f5d1 0.600000000000 1790465 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": 1302902, "vin": [ { "gen": { "height": 1302892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f70b9acdd482017049affbf4cfedb1b095d6e786d5f33734f1aef6dc27f5d1" } } ], "extra": [ 1, 165, 183, 22, 30, 114, 181, 205, 47, 207, 151, 150, 139, 76, 20, 77, 126, 217, 39, 251, 49, 0, 127, 185, 243, 177, 6, 120, 133, 24, 94, 53, 5, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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