Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca73ffc7f96e9f5ad12963947f4f0f6234c98fa166d406ea88cdaa2d44647a3a

Tx prefix hash: 3fa763e6d94e0d6c302e37c164043acd6ee0031e2f55a2d475dc74f9582d63cb
Tx public key: 856112589b7718e0ace8afb862fdb72ae8e14604609049d01fddb9078f0cd1ea
Timestamp: 1713404464 Timestamp [UCT]: 2024-04-18 01:41:04 Age [y:d:h:m:s]: 00:357:23:42:49
Block: 1002858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255939 RingCT/type: yes/0
Extra: 01856112589b7718e0ace8afb862fdb72ae8e14604609049d01fddb9078f0cd1ea02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 616b8ea43d27ed7994ab5d4112235a174df5a0107161e621fed3685ed6093743 0.600000000000 1463386 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": 1002868, "vin": [ { "gen": { "height": 1002858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "616b8ea43d27ed7994ab5d4112235a174df5a0107161e621fed3685ed6093743" } } ], "extra": [ 1, 133, 97, 18, 88, 155, 119, 24, 224, 172, 232, 175, 184, 98, 253, 183, 42, 232, 225, 70, 4, 96, 144, 73, 208, 31, 221, 185, 7, 143, 12, 209, 234, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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