Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55373dcbdd6f37c847f0f8b382a9b858e402ec32d8645425a28eff75e1cdb323

Tx prefix hash: 8f6fa0ad361ed766b095241309b81a0a0e5fac7d2209e5f09cb6f23584c5b198
Tx public key: d5e7a26ce3d19a4800d44bdb90e6aed6e33526a322527773c96fa226934f86a4
Timestamp: 1723721337 Timestamp [UCT]: 2024-08-15 11:28:57 Age [y:d:h:m:s]: 00:101:14:39:34
Block: 1088410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72680 RingCT/type: yes/0
Extra: 01d5e7a26ce3d19a4800d44bdb90e6aed6e33526a322527773c96fa226934f86a4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443bdc11c9c8bfd3aa90768e6ce09748282e8f3178a9cbbf81d306d6055bd62c 0.600000000000 1563025 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": 1088420, "vin": [ { "gen": { "height": 1088410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443bdc11c9c8bfd3aa90768e6ce09748282e8f3178a9cbbf81d306d6055bd62c" } } ], "extra": [ 1, 213, 231, 162, 108, 227, 209, 154, 72, 0, 212, 75, 219, 144, 230, 174, 214, 227, 53, 38, 163, 34, 82, 119, 115, 201, 111, 162, 38, 147, 79, 134, 164, 2, 17, 0, 0, 0, 4, 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