Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3cd5292073e13bf6d7c16be5e283dd7b82fa6ad7b6a6dd5f2e998b014f4df97

Tx prefix hash: 291cf42f1a5163335b45901cc2d2c6d3e167e9770b6bbe73f1c9e7f1a0c57d2a
Tx public key: a74ad7d4fd2f3893c340899f692ef22e7e8b37a9bce4fb4ee4a4a1a79099922e
Timestamp: 1682352106 Timestamp [UCT]: 2023-04-24 16:01:46 Age [y:d:h:m:s]: 01:358:18:47:55
Block: 745686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517683 RingCT/type: yes/0
Extra: 01a74ad7d4fd2f3893c340899f692ef22e7e8b37a9bce4fb4ee4a4a1a79099922e021100000001e7ace25d000000000000000000

1 output(s) for total of 2.076026737000 dcy

stealth address amount amount idx
00: 8f403d99e351dbdf44d686184ded0993d6fb3f8419825b11cee075cc282312bf 2.076026737000 1193159 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": 745696, "vin": [ { "gen": { "height": 745686 } } ], "vout": [ { "amount": 2076026737, "target": { "key": "8f403d99e351dbdf44d686184ded0993d6fb3f8419825b11cee075cc282312bf" } } ], "extra": [ 1, 167, 74, 215, 212, 253, 47, 56, 147, 195, 64, 137, 159, 105, 46, 242, 46, 126, 139, 55, 169, 188, 228, 251, 78, 228, 164, 161, 167, 144, 153, 146, 46, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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