Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14d473a4ccbc6c0f240a1f95651218df14018d1ac4d0a58b7d4b53f8538556cc

Tx prefix hash: 8409651cb2ad5115300b054d3c26899a0fe3e42fdd9dcd666ce179fa4c37cba5
Tx public key: 4ecf0d016375c54b1be4dc6b55b0adafde7f12c6e069e5ff17d1755544a001f2
Timestamp: 1758891285 Timestamp [UCT]: 2025-09-26 12:54:45 Age [y:d:h:m:s]: 00:044:11:31:50
Block: 1376888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31832 RingCT/type: yes/0
Extra: 014ecf0d016375c54b1be4dc6b55b0adafde7f12c6e069e5ff17d1755544a001f202110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02cf8b480982752d8b58766c590bfb15d7310b4d3a432acbee337e39111ab57b 0.600000000000 1864979 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": 1376898, "vin": [ { "gen": { "height": 1376888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02cf8b480982752d8b58766c590bfb15d7310b4d3a432acbee337e39111ab57b" } } ], "extra": [ 1, 78, 207, 13, 1, 99, 117, 197, 75, 27, 228, 220, 107, 85, 176, 173, 175, 222, 127, 18, 198, 224, 105, 229, 255, 23, 209, 117, 85, 68, 160, 1, 242, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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