Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a60090983ae51bc5d960ee8f67ef43236b6024e81d45d1725d270eea2d1af2

Tx prefix hash: 4a8a484840e029b74a537d5d775178279804fca2ae1e0d61626bbac3153149b2
Tx public key: 0e6c663014162ff971126a741419f0d4e1533f49c95bb658aeb3501bf851ff2f
Timestamp: 1737172644 Timestamp [UCT]: 2025-01-18 03:57:24 Age [y:d:h:m:s]: 00:150:22:19:35
Block: 1199768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107587 RingCT/type: yes/0
Extra: 010e6c663014162ff971126a741419f0d4e1533f49c95bb658aeb3501bf851ff2f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: debe94ab1acc93d1b0a5e8374f4b3d992f8d249ebd857af0f01ad4d48d340e9e 0.600000000000 1686401 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": 1199778, "vin": [ { "gen": { "height": 1199768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "debe94ab1acc93d1b0a5e8374f4b3d992f8d249ebd857af0f01ad4d48d340e9e" } } ], "extra": [ 1, 14, 108, 102, 48, 20, 22, 47, 249, 113, 18, 106, 116, 20, 25, 240, 212, 225, 83, 63, 73, 201, 91, 182, 88, 174, 179, 80, 27, 248, 81, 255, 47, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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