Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd852953aa66915700b7659791d80268524d9f009ce12f9584fdd7ba4d8fda4

Tx prefix hash: ae19d3dea1efc5227748b0cc8179f3810e741bb62bd23e58228e29b3f3dcdde2
Tx public key: 63699cd20f8f183b3b076ee2845e4abb5eb12aec174588f4fd3ad8f92e832d02
Timestamp: 1749551325 Timestamp [UCT]: 2025-06-10 10:28:45 Age [y:d:h:m:s]: 00:157:14:09:56
Block: 1302003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110304 RingCT/type: yes/0
Extra: 0163699cd20f8f183b3b076ee2845e4abb5eb12aec174588f4fd3ad8f92e832d02021100000010bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b92e242be5e8edb556f35893b996c51719b8dd76e84580d423f3f578ca11cb2 0.600000000000 1789572 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": 1302013, "vin": [ { "gen": { "height": 1302003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b92e242be5e8edb556f35893b996c51719b8dd76e84580d423f3f578ca11cb2" } } ], "extra": [ 1, 99, 105, 156, 210, 15, 143, 24, 59, 59, 7, 110, 226, 132, 94, 74, 187, 94, 177, 42, 236, 23, 69, 136, 244, 253, 58, 216, 249, 46, 131, 45, 2, 2, 17, 0, 0, 0, 16, 191, 81, 178, 162, 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