Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e576d57359515ae9629e23bde9aee2b8f1b6ddeeaefdfb193383764c4760cb76

Tx prefix hash: 4139e2ae73c8d2f776844c22b24f276f1850a80917e876d2cc3626556ae16289
Tx public key: f13a42367ff32966ac62efb2a9538d6837f80281c360970a95e3b515689ab6b4
Timestamp: 1710588772 Timestamp [UCT]: 2024-03-16 11:32:52 Age [y:d:h:m:s]: 01:058:22:04:08
Block: 979551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303103 RingCT/type: yes/0
Extra: 01f13a42367ff32966ac62efb2a9538d6837f80281c360970a95e3b515689ab6b40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c7c60da9053c81e5a45597405f3c597dd0f0cd1c56479a705fd4e44d2c7e745 0.600000000000 1439588 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": 979561, "vin": [ { "gen": { "height": 979551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c7c60da9053c81e5a45597405f3c597dd0f0cd1c56479a705fd4e44d2c7e745" } } ], "extra": [ 1, 241, 58, 66, 54, 127, 243, 41, 102, 172, 98, 239, 178, 169, 83, 141, 104, 55, 248, 2, 129, 195, 96, 151, 10, 149, 227, 181, 21, 104, 154, 182, 180, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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