Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 007c67a9b000f9c5ee2e7428aa39c5c1b8b4b8f9ab8c70b47048e2177048fc9b

Tx prefix hash: cebe6b1e848fa6b8a8e0e2a9a1dd2c0c07701b2a67e579ae2fd604dcc500e1e1
Tx public key: c936cc1ac09629fe2fbb662391a7ad338d30006b77fe5cd1d4176df7476b9626
Timestamp: 1745791505 Timestamp [UCT]: 2025-04-27 22:05:05 Age [y:d:h:m:s]: 00:011:18:32:02
Block: 1270869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8407 RingCT/type: yes/0
Extra: 01c936cc1ac09629fe2fbb662391a7ad338d30006b77fe5cd1d4176df7476b96260211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4e33b5c4b518d7fae728b5e3e54dee990a239f7e3a25fd343ad68a61ed1cfc3 0.600000000000 1758114 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": 1270879, "vin": [ { "gen": { "height": 1270869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4e33b5c4b518d7fae728b5e3e54dee990a239f7e3a25fd343ad68a61ed1cfc3" } } ], "extra": [ 1, 201, 54, 204, 26, 192, 150, 41, 254, 47, 187, 102, 35, 145, 167, 173, 51, 141, 48, 0, 107, 119, 254, 92, 209, 212, 23, 109, 247, 71, 107, 150, 38, 2, 17, 0, 0, 0, 4, 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