Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c926b850c83067447d24f9fcd3d2a02a29cbdc77ef3204c34849424b2eb5f4be

Tx prefix hash: 42c449e07ddc77d8e65d66ccb4d7a65de4b45c630c78619284d116f945161698
Tx public key: 000613720bbdf370f88a4abc2a6cb4b7b298880bd4ccc8bf2e90658fe61a32df
Timestamp: 1741252017 Timestamp [UCT]: 2025-03-06 09:06:57 Age [y:d:h:m:s]: 00:259:18:58:07
Block: 1233286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183407 RingCT/type: yes/0
Extra: 01000613720bbdf370f88a4abc2a6cb4b7b298880bd4ccc8bf2e90658fe61a32df021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 957bc1de4ecccfbaa69a196e6e4e7ee4b23d9828a01695eabae194d0193708d5 0.600000000000 1720205 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": 1233296, "vin": [ { "gen": { "height": 1233286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "957bc1de4ecccfbaa69a196e6e4e7ee4b23d9828a01695eabae194d0193708d5" } } ], "extra": [ 1, 0, 6, 19, 114, 11, 189, 243, 112, 248, 138, 74, 188, 42, 108, 180, 183, 178, 152, 136, 11, 212, 204, 200, 191, 46, 144, 101, 143, 230, 26, 50, 223, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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