Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5eb08cf5fa4739ca1b56144acbca6bdd590dbb658f2591b91ac7345589c2302

Tx prefix hash: 3bf286cb7de1db6f684b567e076d20f3cba9418c3686a567d0fa2b594c1f7601
Tx public key: aa4dfc32fde1f6f3d9cb7eadff898ec185deb68a166e4c99c0daa0e1a2978192
Timestamp: 1737169621 Timestamp [UCT]: 2025-01-18 03:07:01 Age [y:d:h:m:s]: 00:058:09:23:53
Block: 1199748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41521 RingCT/type: yes/0
Extra: 01aa4dfc32fde1f6f3d9cb7eadff898ec185deb68a166e4c99c0daa0e1a29781920211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c7d91244bebbea827b4b0c61c394d062de8733dfb8fcab36fa223a77ebb0734 0.600000000000 1686381 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": 1199758, "vin": [ { "gen": { "height": 1199748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c7d91244bebbea827b4b0c61c394d062de8733dfb8fcab36fa223a77ebb0734" } } ], "extra": [ 1, 170, 77, 252, 50, 253, 225, 246, 243, 217, 203, 126, 173, 255, 137, 142, 193, 133, 222, 182, 138, 22, 110, 76, 153, 192, 218, 160, 225, 162, 151, 129, 146, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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