Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48de55ac753a526b6a26521bf7984d232bd1a9435697cb8330f65a479a1ca8f6

Tx prefix hash: c1f47aab09fdc09651bda7b66f6421ab14126c53d07a84a9ba28cb10c3a75ee6
Tx public key: e9be2b5849ba4913ab3f337958a75fa1a2a5d821b84d3cddfefedfc71e3c095f
Timestamp: 1760719804 Timestamp [UCT]: 2025-10-17 16:50:04 Age [y:d:h:m:s]: 00:067:06:04:47
Block: 1392032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48132 RingCT/type: yes/0
Extra: 01e9be2b5849ba4913ab3f337958a75fa1a2a5d821b84d3cddfefedfc71e3c095f0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6575369722320220e29aafbf933c2e4dd807072c6ea8a5f8f1cc19625013c42e 0.600000000000 1880283 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": 1392042, "vin": [ { "gen": { "height": 1392032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6575369722320220e29aafbf933c2e4dd807072c6ea8a5f8f1cc19625013c42e" } } ], "extra": [ 1, 233, 190, 43, 88, 73, 186, 73, 19, 171, 63, 51, 121, 88, 167, 95, 161, 162, 165, 216, 33, 184, 77, 60, 221, 254, 254, 223, 199, 30, 60, 9, 95, 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