Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e338783df5cc7affb458f255ffd6f269e07a7bd2fcbb01d557a204f7f595d1

Tx prefix hash: 9cb7a0ff53357f6483434ecf24fcf715a63bddaf7a4f26acc6c476d70e20f908
Tx public key: e7dbac74738766236b341db59c2a53e285a166a0678a5c06df4f2df5ee9346d6
Timestamp: 1717201069 Timestamp [UCT]: 2024-06-01 00:17:49 Age [y:d:h:m:s]: 00:289:11:56:20
Block: 1034357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206907 RingCT/type: yes/0
Extra: 01e7dbac74738766236b341db59c2a53e285a166a0678a5c06df4f2df5ee9346d602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b40edc176bade22f566734294acca92b82de71347b3508a97f975a213c758b0f 0.600000000000 1502860 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": 1034367, "vin": [ { "gen": { "height": 1034357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b40edc176bade22f566734294acca92b82de71347b3508a97f975a213c758b0f" } } ], "extra": [ 1, 231, 219, 172, 116, 115, 135, 102, 35, 107, 52, 29, 181, 156, 42, 83, 226, 133, 161, 102, 160, 103, 138, 92, 6, 223, 79, 45, 245, 238, 147, 70, 214, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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