Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3728402c117daea24d50e7de136effd68c9d2fca012b3c208da2cbe17750806a

Tx prefix hash: f03824f7c242cb55af0e98d0e0844aa6bd3959294a36155fc072f841b03b0ee2
Tx public key: deb5e22df2d4a9d9f38bed6a0411ee72841bfe7284b62ac9775e05d908ba6340
Timestamp: 1712513570 Timestamp [UCT]: 2024-04-07 18:12:50 Age [y:d:h:m:s]: 00:235:01:18:07
Block: 995459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168301 RingCT/type: yes/0
Extra: 01deb5e22df2d4a9d9f38bed6a0411ee72841bfe7284b62ac9775e05d908ba634002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9cc5a625dea05cf433e8f7fec0405db1fa352c74b9a7fed43b6d0c86897929 0.600000000000 1455867 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": 995469, "vin": [ { "gen": { "height": 995459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9cc5a625dea05cf433e8f7fec0405db1fa352c74b9a7fed43b6d0c86897929" } } ], "extra": [ 1, 222, 181, 226, 45, 242, 212, 169, 217, 243, 139, 237, 106, 4, 17, 238, 114, 132, 27, 254, 114, 132, 182, 42, 201, 119, 94, 5, 217, 8, 186, 99, 64, 2, 17, 0, 0, 0, 7, 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