Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d5c1591c13f0fd8c3840c330938a6d3da67f58bbe29d929e441a7896b4bf28

Tx prefix hash: 864e205c219e8cb61eb080b9a97244afd6684eb0d99595791bf5c51bc4ff8210
Tx public key: 15d14a5fffe589a34aae5ebe3663cfebf86f09e187111cb1808a8395ea341f17
Timestamp: 1745238591 Timestamp [UCT]: 2025-04-21 12:29:51 Age [y:d:h:m:s]: 00:023:09:09:35
Block: 1266280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16737 RingCT/type: yes/0
Extra: 0115d14a5fffe589a34aae5ebe3663cfebf86f09e187111cb1808a8395ea341f17021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e64a0a8b1515c70224c611a86b31899232f2ba0b69d57c5f51ac34c999928e3 0.600000000000 1753501 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": 1266290, "vin": [ { "gen": { "height": 1266280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e64a0a8b1515c70224c611a86b31899232f2ba0b69d57c5f51ac34c999928e3" } } ], "extra": [ 1, 21, 209, 74, 95, 255, 229, 137, 163, 74, 174, 94, 190, 54, 99, 207, 235, 248, 111, 9, 225, 135, 17, 28, 177, 128, 138, 131, 149, 234, 52, 31, 23, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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