Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd39f3022bc45e848489c18ebf2b36c8ff6cd1b72992b4bace7945f28c5eef8d

Tx prefix hash: 4021bddb270298077837bc8483fe2468ea742b30b410ffd64024a3fa1ba5dc9e
Tx public key: 54170a8aad5f29e3d3e87b1b9a3da3f45f42cd47134799b67c5909eec70ca434
Timestamp: 1722128490 Timestamp [UCT]: 2024-07-28 01:01:30 Age [y:d:h:m:s]: 00:283:02:38:55
Block: 1075196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202270 RingCT/type: yes/0
Extra: 0154170a8aad5f29e3d3e87b1b9a3da3f45f42cd47134799b67c5909eec70ca434021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ead354c6581d2f5e2b4a43c467f9f97441efb78ff6a349ee08941e92f922281f 0.600000000000 1547719 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": 1075206, "vin": [ { "gen": { "height": 1075196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ead354c6581d2f5e2b4a43c467f9f97441efb78ff6a349ee08941e92f922281f" } } ], "extra": [ 1, 84, 23, 10, 138, 173, 95, 41, 227, 211, 232, 123, 27, 154, 61, 163, 244, 95, 66, 205, 71, 19, 71, 153, 182, 124, 89, 9, 238, 199, 12, 164, 52, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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