Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c8fa981c8c24623344894723a8abad7893877c41c87bd9a89d3351ef6772e8d

Tx prefix hash: 4b51e084f9e1edaa57afdc15c482e87549af32fda95d0bff599b57bc2ff1e6ed
Tx public key: f6845161179a5b8e92b107faba3c7c34a4595e2e4cc3dd24f825ff98baa9776d
Timestamp: 1721710965 Timestamp [UCT]: 2024-07-23 05:02:45 Age [y:d:h:m:s]: 00:254:20:36:38
Block: 1071733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182060 RingCT/type: yes/0
Extra: 01f6845161179a5b8e92b107faba3c7c34a4595e2e4cc3dd24f825ff98baa9776d0211000000028f454fe7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b84489097cae5e3f054b860a0069b4840d8c9401ecc04022d65a94f4314d8b8e 0.600000000000 1544068 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": 1071743, "vin": [ { "gen": { "height": 1071733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b84489097cae5e3f054b860a0069b4840d8c9401ecc04022d65a94f4314d8b8e" } } ], "extra": [ 1, 246, 132, 81, 97, 23, 154, 91, 142, 146, 177, 7, 250, 186, 60, 124, 52, 164, 89, 94, 46, 76, 195, 221, 36, 248, 37, 255, 152, 186, 169, 119, 109, 2, 17, 0, 0, 0, 2, 143, 69, 79, 231, 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