Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af11583230b363a9c71c8ea75448d6792a1eb871724dfd9a110641467d549219

Tx prefix hash: bd5200eab8b0b6dd569a9d49e0742f64281a61d10e2d3b984a548ff08190abc6
Tx public key: f437e351d954b8a354aac4b13e3ef0841995d99afdfe271c0ed9c5ae4672fa6b
Timestamp: 1717103231 Timestamp [UCT]: 2024-05-30 21:07:11 Age [y:d:h:m:s]: 00:356:10:25:32
Block: 1033533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254792 RingCT/type: yes/0
Extra: 01f437e351d954b8a354aac4b13e3ef0841995d99afdfe271c0ed9c5ae4672fa6b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ece8fa7c055f96092e31a7ab3b3aecb94c9ce465ba2aed95ebec01f3bba886a 0.600000000000 1502002 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": 1033543, "vin": [ { "gen": { "height": 1033533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ece8fa7c055f96092e31a7ab3b3aecb94c9ce465ba2aed95ebec01f3bba886a" } } ], "extra": [ 1, 244, 55, 227, 81, 217, 84, 184, 163, 84, 170, 196, 177, 62, 62, 240, 132, 25, 149, 217, 154, 253, 254, 39, 28, 14, 217, 197, 174, 70, 114, 250, 107, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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