Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dafbd08a1c10b78a02c6b3e426cd809d7366f1d0e5ffd4975caa5e1f460f6546

Tx prefix hash: 0da117c05f82d8d753978cf781574b993daf0492b946aae942017267435d71bf
Tx public key: b0aedc92e2887ea601f50713a6a604feed4c5ec3a5800d7335ccf4342bf7ae4b
Timestamp: 1764735293 Timestamp [UCT]: 2025-12-03 04:14:53 Age [y:d:h:m:s]: 00:001:02:43:20
Block: 1425300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798 RingCT/type: yes/0
Extra: 01b0aedc92e2887ea601f50713a6a604feed4c5ec3a5800d7335ccf4342bf7ae4b021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c31c1f92824c5e3ed456bbacfeb38a885b0b469670438e2f12a1bbd305ea575 0.600000000000 1913933 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": 1425310, "vin": [ { "gen": { "height": 1425300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c31c1f92824c5e3ed456bbacfeb38a885b0b469670438e2f12a1bbd305ea575" } } ], "extra": [ 1, 176, 174, 220, 146, 226, 136, 126, 166, 1, 245, 7, 19, 166, 166, 4, 254, 237, 76, 94, 195, 165, 128, 13, 115, 53, 204, 244, 52, 43, 247, 174, 75, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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