Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66d641223ea9b9d4e363b60959138cbafe0ad2f9c7ab1b185d5381a232f478ed

Tx prefix hash: 27fa32031d4f666fa005501916b81c2a4560d8e8ff2fd014a112dbe49eca82e1
Tx public key: e5f633efb283b97bb7449cc39a0ba36e5e5dfc5d3636e57355186d1e24c966d7
Timestamp: 1702768850 Timestamp [UCT]: 2023-12-16 23:20:50 Age [y:d:h:m:s]: 01:035:08:59:25
Block: 914695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286591 RingCT/type: yes/0
Extra: 01e5f633efb283b97bb7449cc39a0ba36e5e5dfc5d3636e57355186d1e24c966d702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8a8d7d3b19736ca9466fc1eccd3cfe1a9af7f429979e0e018544ba12a5caa74 0.600000000000 1372045 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": 914705, "vin": [ { "gen": { "height": 914695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8a8d7d3b19736ca9466fc1eccd3cfe1a9af7f429979e0e018544ba12a5caa74" } } ], "extra": [ 1, 229, 246, 51, 239, 178, 131, 185, 123, 183, 68, 156, 195, 154, 11, 163, 110, 94, 93, 252, 93, 54, 54, 229, 115, 85, 24, 109, 30, 36, 201, 102, 215, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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