Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e10ac3340e0c60aaae1c88570e8696f39e9c2e9bed331ace49faa685f9591e

Tx prefix hash: a675561b235f2b7f92f5c473741925f9d9f07d16af1da577773b14ba751e8a3e
Tx public key: f84a1a4b55be725e00acfabd49de0121f6fefde1abf241370b6e84389c2fe4fd
Timestamp: 1759846891 Timestamp [UCT]: 2025-10-07 14:21:31 Age [y:d:h:m:s]: 00:041:17:14:08
Block: 1384796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29863 RingCT/type: yes/0
Extra: 01f84a1a4b55be725e00acfabd49de0121f6fefde1abf241370b6e84389c2fe4fd021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db75d6525fdc9c0eee3d7416433ddd4d2d1e450d3b952bd71434ccd767cabc34 0.600000000000 1872953 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": 1384806, "vin": [ { "gen": { "height": 1384796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db75d6525fdc9c0eee3d7416433ddd4d2d1e450d3b952bd71434ccd767cabc34" } } ], "extra": [ 1, 248, 74, 26, 75, 85, 190, 114, 94, 0, 172, 250, 189, 73, 222, 1, 33, 246, 254, 253, 225, 171, 242, 65, 55, 11, 110, 132, 56, 156, 47, 228, 253, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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