Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3570584ddec854ccf135cd501472f391a6ceaa37ca4839262144a07286da8beb

Tx prefix hash: 701ab1b9cef608ae287a2d6af114624ec9484ad1c3c5c5f91b5b44b2b351c964
Tx public key: 7428a9cc75e409b06df18c0ab1bc57e103f9e2335e2d6b8a84fee059a3a7520f
Timestamp: 1755615167 Timestamp [UCT]: 2025-08-19 14:52:47 Age [y:d:h:m:s]: 00:092:13:54:36
Block: 1349932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66078 RingCT/type: yes/0
Extra: 017428a9cc75e409b06df18c0ab1bc57e103f9e2335e2d6b8a84fee059a3a7520f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c339db93fcc67f3bc09eff21df142596abd6fd2302254bfe2f15579975444e 0.600000000000 1837871 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": 1349942, "vin": [ { "gen": { "height": 1349932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c339db93fcc67f3bc09eff21df142596abd6fd2302254bfe2f15579975444e" } } ], "extra": [ 1, 116, 40, 169, 204, 117, 228, 9, 176, 109, 241, 140, 10, 177, 188, 87, 225, 3, 249, 226, 51, 94, 45, 107, 138, 132, 254, 224, 89, 163, 167, 82, 15, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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