Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef923b84805febc4e7ac4b252cc4c160b228a698bd34b4014fe5cf37701c76f

Tx prefix hash: 4100e739e2697e15d63502066e8cdf724c9dafa96f8746964728b298923e1d17
Tx public key: 518afd4b028f0228499d3a047d30f3ebe2e4f0e285afdc3e22716173593b6043
Timestamp: 1750302403 Timestamp [UCT]: 2025-06-19 03:06:43 Age [y:d:h:m:s]: 00:222:12:31:52
Block: 1308064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156778 RingCT/type: yes/0
Extra: 01518afd4b028f0228499d3a047d30f3ebe2e4f0e285afdc3e22716173593b6043021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0f1b21c80e07fa3f1ec79b0295b0b52fe5713db33db8a56f932bd575d932ea 0.600000000000 1795677 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": 1308074, "vin": [ { "gen": { "height": 1308064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0f1b21c80e07fa3f1ec79b0295b0b52fe5713db33db8a56f932bd575d932ea" } } ], "extra": [ 1, 81, 138, 253, 75, 2, 143, 2, 40, 73, 157, 58, 4, 125, 48, 243, 235, 226, 228, 240, 226, 133, 175, 220, 62, 34, 113, 97, 115, 89, 59, 96, 67, 2, 17, 0, 0, 0, 6, 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