Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948b82d98ff0089ecd1310efa7bbe0e5a0b761f58aa4a7b1eec91f37f7ee7105

Tx prefix hash: 6c591991ad21781013cdff0fb18a652dd729b114309217a438031ab914eec2e3
Tx public key: 4a4e054508370faa71590377fdf8a5f113fb09737057cacfc4c47048121e9112
Timestamp: 1754275814 Timestamp [UCT]: 2025-08-04 02:50:14 Age [y:d:h:m:s]: 00:062:20:35:36
Block: 1339813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43802 RingCT/type: yes/0
Extra: 014a4e054508370faa71590377fdf8a5f113fb09737057cacfc4c47048121e9112021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45d435f4fd55f28cebf4bd9c39b3db7dbf2c78c477e7d2c6a715e1bfb0a50277 0.600000000000 1827628 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": 1339823, "vin": [ { "gen": { "height": 1339813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45d435f4fd55f28cebf4bd9c39b3db7dbf2c78c477e7d2c6a715e1bfb0a50277" } } ], "extra": [ 1, 74, 78, 5, 69, 8, 55, 15, 170, 113, 89, 3, 119, 253, 248, 165, 241, 19, 251, 9, 115, 112, 87, 202, 207, 196, 196, 112, 72, 18, 30, 145, 18, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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