Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a565c2f875c1712146f69ead99d2a2e047e1f48d0054b3b3a27e59c6cdc20d32

Tx prefix hash: 4a4f49cb001e075fcf0dc77d70079379ac1ae91fb66199fe3837242bfdfaa49b
Tx public key: e8e56fe6a381d33294c6e50c645f5bcf7613dd6df67c3a88a3b328ec8dc06050
Timestamp: 1701324347 Timestamp [UCT]: 2023-11-30 06:05:47 Age [y:d:h:m:s]: 01:164:18:18:45
Block: 902709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378948 RingCT/type: yes/0
Extra: 01e8e56fe6a381d33294c6e50c645f5bcf7613dd6df67c3a88a3b328ec8dc060500211000000024b8f5122000000000000000000

1 output(s) for total of 0.626542203000 dcy

stealth address amount amount idx
00: 0de3f44738a6dc77465d93430e70a9f0384d21c8dad896b7691eaeb40c808623 0.626542203000 1359364 of 0

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": 902719, "vin": [ { "gen": { "height": 902709 } } ], "vout": [ { "amount": 626542203, "target": { "key": "0de3f44738a6dc77465d93430e70a9f0384d21c8dad896b7691eaeb40c808623" } } ], "extra": [ 1, 232, 229, 111, 230, 163, 129, 211, 50, 148, 198, 229, 12, 100, 95, 91, 207, 118, 19, 221, 109, 246, 124, 58, 136, 163, 179, 40, 236, 141, 192, 96, 80, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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