Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd99060f5c8442db3e52f3db43369581fdb86e6d6dce49216d1ffd30482a69d

Tx prefix hash: 546e7377844bba0a7c0d54d177bcbeef21be15686b7614c695ebac5c23e89218
Tx public key: 97001703c945828039d5a1f04bfecc3c25d5be5ee29829f0c3c0c873fd26b95d
Timestamp: 1767371642 Timestamp [UCT]: 2026-01-02 16:34:02 Age [y:d:h:m:s]: 00:000:17:48:03
Block: 1447157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 535 RingCT/type: yes/0
Extra: 0197001703c945828039d5a1f04bfecc3c25d5be5ee29829f0c3c0c873fd26b95d020900000001f3b3285400

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdcdfbb938db857a1d1d2fb40829198b60f118c30e22382d7dee0969f47da99e 0.600000000000 1936115 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": 1447167, "vin": [ { "gen": { "height": 1447157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdcdfbb938db857a1d1d2fb40829198b60f118c30e22382d7dee0969f47da99e" } } ], "extra": [ 1, 151, 0, 23, 3, 201, 69, 130, 128, 57, 213, 161, 240, 75, 254, 204, 60, 37, 213, 190, 94, 226, 152, 41, 240, 195, 192, 200, 115, 253, 38, 185, 93, 2, 9, 0, 0, 0, 1, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8