Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d7ac77ef35010ff0777029e68bdf36676bbf6322b84d54f5ab49e872af0f28

Tx prefix hash: e9e9e7cef60634bc8e245e6ffffb7d7a7373aa96733133e2dadcb2c3d31eb964
Tx public key: 0cc3a7d4a308d6645a135d1f32a20b73634c49d5f236a4d084a65ee681e8a27a
Timestamp: 1747389201 Timestamp [UCT]: 2025-05-16 09:53:21 Age [y:d:h:m:s]: 00:237:00:53:31
Block: 1284087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167191 RingCT/type: yes/0
Extra: 010cc3a7d4a308d6645a135d1f32a20b73634c49d5f236a4d084a65ee681e8a27a0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f43536e03b3c33df268f95cec5e2094cf34ebcb1123fdfbb19693c32e6650e 0.600000000000 1771522 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": 1284097, "vin": [ { "gen": { "height": 1284087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f43536e03b3c33df268f95cec5e2094cf34ebcb1123fdfbb19693c32e6650e" } } ], "extra": [ 1, 12, 195, 167, 212, 163, 8, 214, 100, 90, 19, 93, 31, 50, 162, 11, 115, 99, 76, 73, 213, 242, 54, 164, 208, 132, 166, 94, 230, 129, 232, 162, 122, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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