Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e695a1c38f04bc621277f048e012f4229f830ec871389f3501c2703a14d94d4

Tx prefix hash: d9993c4841b974f46854e3630f0a623924e72185ba8caa1d08d9c5fc67bbc3a8
Tx public key: f5b2f2609092cff322df1887acd2350800a6caaba568ad57ad8bca44b62db60e
Timestamp: 1758503404 Timestamp [UCT]: 2025-09-22 01:10:04 Age [y:d:h:m:s]: 00:052:18:40:26
Block: 1373655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37783 RingCT/type: yes/0
Extra: 01f5b2f2609092cff322df1887acd2350800a6caaba568ad57ad8bca44b62db60e021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4260c99431ba091a4fd9ea3dd8c281d6a43f2dad5ec1ffcc8b474f29c42f0a9c 0.600000000000 1861740 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": 1373665, "vin": [ { "gen": { "height": 1373655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4260c99431ba091a4fd9ea3dd8c281d6a43f2dad5ec1ffcc8b474f29c42f0a9c" } } ], "extra": [ 1, 245, 178, 242, 96, 144, 146, 207, 243, 34, 223, 24, 135, 172, 210, 53, 8, 0, 166, 202, 171, 165, 104, 173, 87, 173, 139, 202, 68, 182, 45, 182, 14, 2, 17, 0, 0, 0, 1, 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