Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8e8c522af693c7234189948af9cbcbf84e683c3d97a5562d28e8fdd46cfc24

Tx prefix hash: b13f442486bd8e7e5d44ebf2947c4afe45782ddb41c68dc7f5b2cef4bf742052
Tx public key: bdc3ca00a01b499115b8b94bfde802c60d84d5bd681eeb4f18648e30491865a6
Timestamp: 1765952868 Timestamp [UCT]: 2025-12-17 06:27:48 Age [y:d:h:m:s]: 00:022:12:02:21
Block: 1435385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16124 RingCT/type: yes/0
Extra: 01bdc3ca00a01b499115b8b94bfde802c60d84d5bd681eeb4f18648e30491865a60211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d728834bf1a0a650191cd59c6a7cfe5640073ce731ccbfa04b8d10d1ed912563 0.600000000000 1924182 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": 1435395, "vin": [ { "gen": { "height": 1435385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d728834bf1a0a650191cd59c6a7cfe5640073ce731ccbfa04b8d10d1ed912563" } } ], "extra": [ 1, 189, 195, 202, 0, 160, 27, 73, 145, 21, 184, 185, 75, 253, 232, 2, 198, 13, 132, 213, 189, 104, 30, 235, 79, 24, 100, 142, 48, 73, 24, 101, 166, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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