Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c922157e0d2f85bd6ad3daf1a33fe64539e16c9a920779f1c0b94ca8d1f69196

Tx prefix hash: 57286ff88d24faf896c12c58d9884d679fce83717663cf0d4b22a226ad10cb3e
Tx public key: ada32bb7b0a81e2713aa717ef8ab45355b1b49c037b12084547e155397bf9219
Timestamp: 1700614640 Timestamp [UCT]: 2023-11-22 00:57:20 Age [y:d:h:m:s]: 01:136:05:06:34
Block: 896841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358522 RingCT/type: yes/0
Extra: 01ada32bb7b0a81e2713aa717ef8ab45355b1b49c037b12084547e155397bf921902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.655229525000 dcy

stealth address amount amount idx
00: 187f2b29cbbddb77a5fb24ca036056ee04b843214620a63d00e73e6fb0dec241 0.655229525000 1353184 of 0

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": 896851, "vin": [ { "gen": { "height": 896841 } } ], "vout": [ { "amount": 655229525, "target": { "key": "187f2b29cbbddb77a5fb24ca036056ee04b843214620a63d00e73e6fb0dec241" } } ], "extra": [ 1, 173, 163, 43, 183, 176, 168, 30, 39, 19, 170, 113, 126, 248, 171, 69, 53, 91, 27, 73, 192, 55, 177, 32, 132, 84, 126, 21, 83, 151, 191, 146, 25, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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