Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f578fae6931d523ee4e8c0512d3cfa7cc103ae116ba1c84ea11b5c8a3b73796

Tx prefix hash: 3bd2d6bd75b7d072ba7bc3b7afd08625727b9c7ef30acef6b78a72455c2fb224
Tx public key: 5aea708f8cb6ba6593ae10967020996c5f651ed35966b7247eebc712b476659d
Timestamp: 1751690764 Timestamp [UCT]: 2025-07-05 04:46:04 Age [y:d:h:m:s]: 00:139:09:47:07
Block: 1319052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97954 RingCT/type: yes/0
Extra: 015aea708f8cb6ba6593ae10967020996c5f651ed35966b7247eebc712b476659d02110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67cb670a2d15d95accc97c591c85bfac5b6d829a79a69f7f2f7e11883c8db253 0.600000000000 1806741 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": 1319062, "vin": [ { "gen": { "height": 1319052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67cb670a2d15d95accc97c591c85bfac5b6d829a79a69f7f2f7e11883c8db253" } } ], "extra": [ 1, 90, 234, 112, 143, 140, 182, 186, 101, 147, 174, 16, 150, 112, 32, 153, 108, 95, 101, 30, 211, 89, 102, 183, 36, 126, 235, 199, 18, 180, 118, 101, 157, 2, 17, 0, 0, 0, 9, 67, 132, 109, 102, 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