Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff94ee87b6cf50444dc8e2d05082a00e54c069de7e74f2f7aa4eb8e97947ba50

Tx prefix hash: 54ef528ebcfb84850dbec64ddd37da496fcbdf34d7c1286f0791f43915b215c4
Tx public key: 6a8414535a8e2d189a67a3a8f55950c2da483b96c82cb907da9c99496863445c
Timestamp: 1729216933 Timestamp [UCT]: 2024-10-18 02:02:13 Age [y:d:h:m:s]: 00:096:02:47:37
Block: 1133974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68645 RingCT/type: yes/0
Extra: 016a8414535a8e2d189a67a3a8f55950c2da483b96c82cb907da9c99496863445c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 700f5812bdedb3b866a9c8b76335180db5b4f1f2f61f74cff9492d9b59329f78 0.600000000000 1617203 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": 1133984, "vin": [ { "gen": { "height": 1133974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "700f5812bdedb3b866a9c8b76335180db5b4f1f2f61f74cff9492d9b59329f78" } } ], "extra": [ 1, 106, 132, 20, 83, 90, 142, 45, 24, 154, 103, 163, 168, 245, 89, 80, 194, 218, 72, 59, 150, 200, 44, 185, 7, 218, 156, 153, 73, 104, 99, 68, 92, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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