Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e9c8d4a73ae92cf45102ca4ce70819baaec139fb0ed4d8f8b812a091a1bf91

Tx prefix hash: 153012fbd17f37355d150ae425b28bf8004f65c48c1b6090d42a4c7affa641a7
Tx public key: 15492e58aa0450aaf64c076fcc9b23cff842574bb41f8944da2276a644b2b4c3
Timestamp: 1763322604 Timestamp [UCT]: 2025-11-16 19:50:04 Age [y:d:h:m:s]: 00:011:10:33:57
Block: 1413596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8191 RingCT/type: yes/0
Extra: 0115492e58aa0450aaf64c076fcc9b23cff842574bb41f8944da2276a644b2b4c302110000000643b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5756d119521625a522c903da1a0b61c97b26c9bf6a36fb5d621b0df38fe6a6 0.600000000000 1902075 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": 1413606, "vin": [ { "gen": { "height": 1413596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5756d119521625a522c903da1a0b61c97b26c9bf6a36fb5d621b0df38fe6a6" } } ], "extra": [ 1, 21, 73, 46, 88, 170, 4, 80, 170, 246, 76, 7, 111, 204, 155, 35, 207, 248, 66, 87, 75, 180, 31, 137, 68, 218, 34, 118, 166, 68, 178, 180, 195, 2, 17, 0, 0, 0, 6, 67, 181, 4, 113, 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