Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5be9f53589e248f81ee8d7d2d78533d5bc3369e3c8da933e7c4573d400ae1984

Tx prefix hash: 083cb5e5a2067f67f1e0efcb004414ad64c9e74f7ef67720518e46fca4e4bfc8
Tx public key: 6faadb815a537178d60b440221a08704715bf9e0a8bdf5ec7222fbf8a99fd293
Timestamp: 1726237959 Timestamp [UCT]: 2024-09-13 14:32:39 Age [y:d:h:m:s]: 00:207:18:58:31
Block: 1109265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148346 RingCT/type: yes/0
Extra: 016faadb815a537178d60b440221a08704715bf9e0a8bdf5ec7222fbf8a99fd29302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45114485fbb4dfc415b91cc348b28143e19f1a6fb0e1981b52d3cc2abd7428db 0.600000000000 1587456 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": 1109275, "vin": [ { "gen": { "height": 1109265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45114485fbb4dfc415b91cc348b28143e19f1a6fb0e1981b52d3cc2abd7428db" } } ], "extra": [ 1, 111, 170, 219, 129, 90, 83, 113, 120, 214, 11, 68, 2, 33, 160, 135, 4, 113, 91, 249, 224, 168, 189, 245, 236, 114, 34, 251, 248, 169, 159, 210, 147, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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