Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ae11dfe5bffec4dd02749a3c94846fa3c56f94e4568f84abe7b05229d5169d

Tx prefix hash: 244891a6e9aed4efbbc0e19cc8ea823fb04c1134c78041bd8d90371b57dff180
Tx public key: e7ed06cbc12f97f45e170984f629f72c8fbfc4f9f4cbc77e6b07a7969fe14872
Timestamp: 1708291517 Timestamp [UCT]: 2024-02-18 21:25:17 Age [y:d:h:m:s]: 01:271:00:57:25
Block: 960493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452464 RingCT/type: yes/0
Extra: 01e7ed06cbc12f97f45e170984f629f72c8fbfc4f9f4cbc77e6b07a7969fe1487202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c9b64ec93612cfd3d90af3bcab5000bd21fc17ca097ff58b8327b8698b601f 0.600000000000 1420064 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": 960503, "vin": [ { "gen": { "height": 960493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c9b64ec93612cfd3d90af3bcab5000bd21fc17ca097ff58b8327b8698b601f" } } ], "extra": [ 1, 231, 237, 6, 203, 193, 47, 151, 244, 94, 23, 9, 132, 246, 41, 247, 44, 143, 191, 196, 249, 244, 203, 199, 126, 107, 7, 167, 150, 159, 225, 72, 114, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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