Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999bcbda1b65795d5e221b38e39dfa9c6ea5342d7e74ab49e9145372db75d922

Tx prefix hash: 23229a4f0f72727de5baadb256709f277f0dc78738bfaa5e756f2344e344d070
Tx public key: 804f6e3b4cb425c860aa766d1cb357b98831d3ed70f270757e5e18c07846c04d
Timestamp: 1757979990 Timestamp [UCT]: 2025-09-15 23:46:30 Age [y:d:h:m:s]: 00:112:21:59:26
Block: 1369321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80850 RingCT/type: yes/0
Extra: 01804f6e3b4cb425c860aa766d1cb357b98831d3ed70f270757e5e18c07846c04d02110000000ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f3486116fd258f242244919402650581354fc7de20f4b1fb3619aac29085c00 0.600000000000 1857396 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": 1369331, "vin": [ { "gen": { "height": 1369321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f3486116fd258f242244919402650581354fc7de20f4b1fb3619aac29085c00" } } ], "extra": [ 1, 128, 79, 110, 59, 76, 180, 37, 200, 96, 170, 118, 109, 28, 179, 87, 185, 136, 49, 211, 237, 112, 242, 112, 117, 126, 94, 24, 192, 120, 70, 192, 77, 2, 17, 0, 0, 0, 10, 178, 247, 132, 196, 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