Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2d913e934080440ceb875642f6e7b597b3546e7b1c084c6558482364aa73b14

Tx prefix hash: 4e233c924ede8657c2e37e5f45bb9b4d520f043d1944b4677114f3426596e107
Tx public key: dd7ca49cb2c3d54266a92ac01e969f3e9084b8f02e6c42d882eb09ac9029f9b7
Timestamp: 1723021012 Timestamp [UCT]: 2024-08-07 08:56:52 Age [y:d:h:m:s]: 01:131:12:35:34
Block: 1082595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352524 RingCT/type: yes/0
Extra: 01dd7ca49cb2c3d54266a92ac01e969f3e9084b8f02e6c42d882eb09ac9029f9b7021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a686c61982d0faa1979290ee1bc62933d3ef79779e67c4e6dfa89c38b71ff6b 0.600000000000 1556424 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": 1082605, "vin": [ { "gen": { "height": 1082595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a686c61982d0faa1979290ee1bc62933d3ef79779e67c4e6dfa89c38b71ff6b" } } ], "extra": [ 1, 221, 124, 164, 156, 178, 195, 213, 66, 102, 169, 42, 192, 30, 150, 159, 62, 144, 132, 184, 240, 46, 108, 66, 216, 130, 235, 9, 172, 144, 41, 249, 183, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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