Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 285e1df421e00c171a11824f96308de709293c9929cd4a660f6cdf8fe04353fa

Tx prefix hash: f915ad7ddadc06138dcc9450574b9da47ccf2559f1fd6acdc770ab1ecf7bd988
Tx public key: 5d77964cb7802264d755045722b8a9447ddd7311a8713dd56f6b6ec591df9ba5
Timestamp: 1711317388 Timestamp [UCT]: 2024-03-24 21:56:28 Age [y:d:h:m:s]: 01:236:18:40:42
Block: 985594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427901 RingCT/type: yes/0
Extra: 015d77964cb7802264d755045722b8a9447ddd7311a8713dd56f6b6ec591df9ba50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 201ef9d0ee752ae2f0c60120bf0f808c219b944b7aa6ff8e65e86bc3fd7fd92b 0.600000000000 1445811 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": 985604, "vin": [ { "gen": { "height": 985594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "201ef9d0ee752ae2f0c60120bf0f808c219b944b7aa6ff8e65e86bc3fd7fd92b" } } ], "extra": [ 1, 93, 119, 150, 76, 183, 128, 34, 100, 215, 85, 4, 87, 34, 184, 169, 68, 125, 221, 115, 17, 168, 113, 61, 213, 111, 107, 110, 197, 145, 223, 155, 165, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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