Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0d97b9bf6da56fa65d037eeb98a8a4ab483e0eadfe0a9ca67f86a8e8a0391c

Tx prefix hash: e105a1f56ae415ad0bd3cadaeb8d3adcbb053b31a8be3e8b84fb0bfeaf5f48c9
Tx public key: 900e9ecc642f0e87849222030dab8759037e647fa2ea0f2262df4e2054a54a69
Timestamp: 1757614129 Timestamp [UCT]: 2025-09-11 18:08:49 Age [y:d:h:m:s]: 00:134:17:12:51
Block: 1366275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96291 RingCT/type: yes/0
Extra: 01900e9ecc642f0e87849222030dab8759037e647fa2ea0f2262df4e2054a54a69021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ea16f000d0dde422f13b4337aa0c23d2bd3be5293d5077a9c97005d04bb7985 0.600000000000 1854314 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": 1366285, "vin": [ { "gen": { "height": 1366275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ea16f000d0dde422f13b4337aa0c23d2bd3be5293d5077a9c97005d04bb7985" } } ], "extra": [ 1, 144, 14, 158, 204, 100, 47, 14, 135, 132, 146, 34, 3, 13, 171, 135, 89, 3, 126, 100, 127, 162, 234, 15, 34, 98, 223, 78, 32, 84, 165, 74, 105, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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