Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879a2517b2b191b346f1a4a4c65ea4e8ce1699007baa16aca8214d470a2a7fcd

Tx prefix hash: 7b08e863e4e8841fbb2b46fb4754001d41b91557f5473362df4de2b9a0977c1a
Tx public key: 3ab914c0277c1bc1e49832a2207afa74474afb5957bf08b3bdaceca73b4ec479
Timestamp: 1710360564 Timestamp [UCT]: 2024-03-13 20:09:24 Age [y:d:h:m:s]: 01:027:12:23:57
Block: 977661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280637 RingCT/type: yes/0
Extra: 013ab914c0277c1bc1e49832a2207afa74474afb5957bf08b3bdaceca73b4ec47902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05418de48d1f8e7a5d7ba5ff77dd6fd4fa3a825a6c4b3328a38130860e49fbe9 0.600000000000 1437664 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": 977671, "vin": [ { "gen": { "height": 977661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05418de48d1f8e7a5d7ba5ff77dd6fd4fa3a825a6c4b3328a38130860e49fbe9" } } ], "extra": [ 1, 58, 185, 20, 192, 39, 124, 27, 193, 228, 152, 50, 162, 32, 122, 250, 116, 71, 74, 251, 89, 87, 191, 8, 179, 189, 172, 236, 167, 59, 78, 196, 121, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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