Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689bc1ce13b130a63b1f4c0bf9db99d3d3bf58ce7470e3d5c055c77b6cd96e35

Tx prefix hash: ab6e8c29b4ec709a6e4bcea04eed6ac15400a9c305c4bde901439c8d5a85019c
Tx public key: f453e9de61e9c8af947879f7f6c3c63f1b052fd1a2a75dd4e15e507fc1a98625
Timestamp: 1691775022 Timestamp [UCT]: 2023-08-11 17:30:22 Age [y:d:h:m:s]: 01:239:12:27:48
Block: 823715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432345 RingCT/type: yes/0
Extra: 01f453e9de61e9c8af947879f7f6c3c63f1b052fd1a2a75dd4e15e507fc1a9862502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.144696513000 dcy

stealth address amount amount idx
00: 2e6aa0b70198e35b2f0d2bd4c90db97dfb35a2242a8a53e8a4f6265bcdd8cc19 1.144696513000 1275929 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": 823725, "vin": [ { "gen": { "height": 823715 } } ], "vout": [ { "amount": 1144696513, "target": { "key": "2e6aa0b70198e35b2f0d2bd4c90db97dfb35a2242a8a53e8a4f6265bcdd8cc19" } } ], "extra": [ 1, 244, 83, 233, 222, 97, 233, 200, 175, 148, 120, 121, 247, 246, 195, 198, 63, 27, 5, 47, 209, 162, 167, 93, 212, 225, 94, 80, 127, 193, 169, 134, 37, 2, 17, 0, 0, 0, 2, 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