Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 851ce1d0c1f9457f45bcab60fd24e162ac3147e32dc5c6dd46163f0d3cc67dbc

Tx prefix hash: e83e30a8f72507e9114d57bcba630b4508a830f8ee04802d74ea89213da34901
Tx public key: 54c2c4d848f86f511cfe227c7a1e489652f527dc60f798366be4e47ff455ebb9
Timestamp: 1724642277 Timestamp [UCT]: 2024-08-26 03:17:57 Age [y:d:h:m:s]: 00:240:23:47:54
Block: 1096035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172110 RingCT/type: yes/0
Extra: 0154c2c4d848f86f511cfe227c7a1e489652f527dc60f798366be4e47ff455ebb9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 582458dc6db0bfe8113da4a6bd4566ebf8aa13d0bc1cc46ab59204a58eed69ea 0.600000000000 1571222 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": 1096045, "vin": [ { "gen": { "height": 1096035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "582458dc6db0bfe8113da4a6bd4566ebf8aa13d0bc1cc46ab59204a58eed69ea" } } ], "extra": [ 1, 84, 194, 196, 216, 72, 248, 111, 81, 28, 254, 34, 124, 122, 30, 72, 150, 82, 245, 39, 220, 96, 247, 152, 54, 107, 228, 228, 127, 244, 85, 235, 185, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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