Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34cbf5bbb5009ee67951b6acea40b8a7a1490f933cc8dad0a067a67030fe3d30

Tx prefix hash: 3f06d23f2ac7dc725b2e4123087facb4621cf7b95548e0492ee0b5d3b4ef30c9
Tx public key: 6835d4c7a648597a3d123e7dfe3c1c89ee8d0afcfee6de037561e94a60262271
Timestamp: 1718488781 Timestamp [UCT]: 2024-06-15 21:59:41 Age [y:d:h:m:s]: 00:220:22:46:21
Block: 1045045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158052 RingCT/type: yes/0
Extra: 016835d4c7a648597a3d123e7dfe3c1c89ee8d0afcfee6de037561e94a602622710211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2a2dbfa494e5cfbc7d8dfdea235f72461c39a179af2573d14ac85b812ccc07f 0.600000000000 1514514 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": 1045055, "vin": [ { "gen": { "height": 1045045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2a2dbfa494e5cfbc7d8dfdea235f72461c39a179af2573d14ac85b812ccc07f" } } ], "extra": [ 1, 104, 53, 212, 199, 166, 72, 89, 122, 61, 18, 62, 125, 254, 60, 28, 137, 238, 141, 10, 252, 254, 230, 222, 3, 117, 97, 233, 74, 96, 38, 34, 113, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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