Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916e099c1bd0871fb0a2fa661ebe0202a226615df12aae193ae86ed3c8720c76

Tx prefix hash: 051b4527a9dbc1e2a562868b20a75adc4db27140b512d25eab47df332a8ba41b
Tx public key: 7af9a5c988e271676b577e22a2a249bf357ef30d770729da39510a8bd3e8162d
Timestamp: 1750604336 Timestamp [UCT]: 2025-06-22 14:58:56 Age [y:d:h:m:s]: 00:151:07:28:24
Block: 1310513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106017 RingCT/type: yes/0
Extra: 017af9a5c988e271676b577e22a2a249bf357ef30d770729da39510a8bd3e8162d02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2056a445e751cac1c1c43784031a8a883ec13e4f5966c0aab9a1bda37452a9b6 0.600000000000 1798134 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": 1310523, "vin": [ { "gen": { "height": 1310513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2056a445e751cac1c1c43784031a8a883ec13e4f5966c0aab9a1bda37452a9b6" } } ], "extra": [ 1, 122, 249, 165, 201, 136, 226, 113, 103, 107, 87, 126, 34, 162, 162, 73, 191, 53, 126, 243, 13, 119, 7, 41, 218, 57, 81, 10, 139, 211, 232, 22, 45, 2, 17, 0, 0, 0, 3, 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