Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07b8256af4e1387556d7a3fe44e4795b6ea13d560a6e1785f3ba2689fce520b1

Tx prefix hash: 369bc2ef1390b90b43e50be3086d6772848a42ae7315c67ab5c7cb67b7c9c40b
Tx public key: 707e0ea78793e61773ea076c57167584ac169b3b7c007598535684273c4b8ecf
Timestamp: 1745121969 Timestamp [UCT]: 2025-04-20 04:06:09 Age [y:d:h:m:s]: 00:215:10:36:21
Block: 1265317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151697 RingCT/type: yes/0
Extra: 01707e0ea78793e61773ea076c57167584ac169b3b7c007598535684273c4b8ecf021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5dce7672a1f12a9b6efc53438a1e3d2129917f62a92354418d896c6003a3b2 0.600000000000 1752524 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": 1265327, "vin": [ { "gen": { "height": 1265317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5dce7672a1f12a9b6efc53438a1e3d2129917f62a92354418d896c6003a3b2" } } ], "extra": [ 1, 112, 126, 14, 167, 135, 147, 230, 23, 115, 234, 7, 108, 87, 22, 117, 132, 172, 22, 155, 59, 124, 0, 117, 152, 83, 86, 132, 39, 60, 75, 142, 207, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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