Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8d810622047abad0562b613dfabd2425fbd43430fe1724630a7aa32515b4f5

Tx prefix hash: d02d11208c9733bc5328d5d12e5526b64111f019ce86a0c74973131d55e279aa
Tx public key: 680da1b1d4b5f003b7449e36e5c370dbbc1466f15672b78d94135fbe8c4a5f53
Timestamp: 1745107395 Timestamp [UCT]: 2025-04-20 00:03:15 Age [y:d:h:m:s]: 00:286:16:55:05
Block: 1265202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202547 RingCT/type: yes/0
Extra: 01680da1b1d4b5f003b7449e36e5c370dbbc1466f15672b78d94135fbe8c4a5f530211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bbf7fd3c4953f703fe5b3aa2dc6c352f47d950c250ca07dde7f68e10c251f30 0.600000000000 1752405 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": 1265212, "vin": [ { "gen": { "height": 1265202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bbf7fd3c4953f703fe5b3aa2dc6c352f47d950c250ca07dde7f68e10c251f30" } } ], "extra": [ 1, 104, 13, 161, 177, 212, 181, 240, 3, 183, 68, 158, 54, 229, 195, 112, 219, 188, 20, 102, 241, 86, 114, 183, 141, 148, 19, 95, 190, 140, 74, 95, 83, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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