Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a6fc7308b900c0554cd68cf3f6eef797bfa738f0715f6489d03eb7b1dbd1da

Tx prefix hash: 793935aa732c29939d19d2a3882136815697e24cfafc3f17b8c4a60aa1f05991
Tx public key: 925fe404cbf90b1aa07053cb2396ca1cac284fd5e9cade0529002ee4f46877b1
Timestamp: 1713126937 Timestamp [UCT]: 2024-04-14 20:35:37 Age [y:d:h:m:s]: 01:207:07:02:15
Block: 1000555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406827 RingCT/type: yes/0
Extra: 01925fe404cbf90b1aa07053cb2396ca1cac284fd5e9cade0529002ee4f46877b10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409fd2a2e3e6effedd67bc27bcc54fd08f4a145c7295e2e0e8d0fede7ba3ae8f 0.600000000000 1461053 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": 1000565, "vin": [ { "gen": { "height": 1000555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409fd2a2e3e6effedd67bc27bcc54fd08f4a145c7295e2e0e8d0fede7ba3ae8f" } } ], "extra": [ 1, 146, 95, 228, 4, 203, 249, 11, 26, 160, 112, 83, 203, 35, 150, 202, 28, 172, 40, 79, 213, 233, 202, 222, 5, 41, 0, 46, 228, 244, 104, 119, 177, 2, 17, 0, 0, 0, 5, 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