Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5b8b6c32d07703727b8d61107720feef0541acae59b68191712a0471a048abf

Tx prefix hash: 06c0440883315158425c6a428eb294c1e5836f20177acfb3d35e9b97a35aa4aa
Tx public key: d1553ee18e964dbab6af084f41092345523211f4ace1c9b7c65bfba42561e5ea
Timestamp: 1761802880 Timestamp [UCT]: 2025-10-30 05:41:20 Age [y:d:h:m:s]: 00:070:15:04:27
Block: 1401008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50570 RingCT/type: yes/0
Extra: 01d1553ee18e964dbab6af084f41092345523211f4ace1c9b7c65bfba42561e5ea021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08353ed939f91dc1b8d6328c95bf25a17d49c7ed3c01a1946762a1dfc066d72d 0.600000000000 1889327 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": 1401018, "vin": [ { "gen": { "height": 1401008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08353ed939f91dc1b8d6328c95bf25a17d49c7ed3c01a1946762a1dfc066d72d" } } ], "extra": [ 1, 209, 85, 62, 225, 142, 150, 77, 186, 182, 175, 8, 79, 65, 9, 35, 69, 82, 50, 17, 244, 172, 225, 201, 183, 198, 91, 251, 164, 37, 97, 229, 234, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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