Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b53b0b72ebea8551a18e68bdf89aec2b031a105ecfd330c4e61b68d5d7f428

Tx prefix hash: be9b1f8636014087939f6282ef5dbed5c908ffb0256852eef50d497e9cb3bb9f
Tx public key: f68466304b0a15e30e1c2a819ee97d70a02bf6c396e07a3892d471e4e8fefa5e
Timestamp: 1755916074 Timestamp [UCT]: 2025-08-23 02:27:54 Age [y:d:h:m:s]: 00:132:07:07:49
Block: 1352391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94555 RingCT/type: yes/0
Extra: 01f68466304b0a15e30e1c2a819ee97d70a02bf6c396e07a3892d471e4e8fefa5e0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3321f96a8507722f347ac6f1ba3395c49913c4ada79025786e833d0cb643b7f6 0.600000000000 1840356 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": 1352401, "vin": [ { "gen": { "height": 1352391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3321f96a8507722f347ac6f1ba3395c49913c4ada79025786e833d0cb643b7f6" } } ], "extra": [ 1, 246, 132, 102, 48, 75, 10, 21, 227, 14, 28, 42, 129, 158, 233, 125, 112, 160, 43, 246, 195, 150, 224, 122, 56, 146, 212, 113, 228, 232, 254, 250, 94, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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