Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af8acd12ef63a0c8b4728759412961bafe06f58ce9fa3cd8a4b4d091e40cdf95

Tx prefix hash: 3243207a11c4b9295214e76ce0f050979114de7f09d4e6f2214022c902e1741e
Tx public key: 393b9443d931db1523bcbeb9de6bcaf987d68ac8f7d2f2dd304a12fd79c94db0
Timestamp: 1742716406 Timestamp [UCT]: 2025-03-23 07:53:26 Age [y:d:h:m:s]: 00:048:08:04:49
Block: 1245413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34563 RingCT/type: yes/0
Extra: 01393b9443d931db1523bcbeb9de6bcaf987d68ac8f7d2f2dd304a12fd79c94db002110000001cca0c97f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c94083d14fcd31b52af8728d42b08ae65d1723c4aa00c02c81f68c2a104bd12e 0.600000000000 1732404 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": 1245423, "vin": [ { "gen": { "height": 1245413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c94083d14fcd31b52af8728d42b08ae65d1723c4aa00c02c81f68c2a104bd12e" } } ], "extra": [ 1, 57, 59, 148, 67, 217, 49, 219, 21, 35, 188, 190, 185, 222, 107, 202, 249, 135, 214, 138, 200, 247, 210, 242, 221, 48, 74, 18, 253, 121, 201, 77, 176, 2, 17, 0, 0, 0, 28, 202, 12, 151, 245, 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