Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c394fe21e0584ce6e7d84e1cbdaf5c4dac9a44d618d22eb7144319b86c66b45

Tx prefix hash: 7bd4596638588f231dfd31cd0ac7f0efa6ce97d9305b1a44c15fa6a278ab0cde
Tx public key: 3b6e2cee0c34f3e57421c226d392c7849faba8af4782149619258ec0b3f1ad4c
Timestamp: 1633092384 Timestamp [UCT]: 2021-10-01 12:46:24 Age [y:d:h:m:s]: 03:061:22:46:11
Block: 344477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 821198 RingCT/type: yes/0
Extra: 013b6e2cee0c34f3e57421c226d392c7849faba8af4782149619258ec0b3f1ad4c021100000001a272b9cb000000000000000000

1 output(s) for total of 44.320548651000 dcy

stealth address amount amount idx
00: ab160a63c8d4a31a3a90dbccf41e8a2072973f7f495667254d5d49fb97a85b44 44.320548651000 706819 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": 344487, "vin": [ { "gen": { "height": 344477 } } ], "vout": [ { "amount": 44320548651, "target": { "key": "ab160a63c8d4a31a3a90dbccf41e8a2072973f7f495667254d5d49fb97a85b44" } } ], "extra": [ 1, 59, 110, 44, 238, 12, 52, 243, 229, 116, 33, 194, 38, 211, 146, 199, 132, 159, 171, 168, 175, 71, 130, 20, 150, 25, 37, 142, 192, 179, 241, 173, 76, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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