Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14b3153f6ffc7a141674f6bcf6b53b66b9babdc8d0a79836530852e6c9aca2a

Tx prefix hash: c9321cd250374a0ef02d8e54bcc86d279fe474144dac17af19c8fdb355889dd9
Tx public key: a9648d25fc0acca319e9ece4d96213b913f48e9bf843110275afea966f257e62
Timestamp: 1700669552 Timestamp [UCT]: 2023-11-22 16:12:32 Age [y:d:h:m:s]: 01:131:10:55:13
Block: 897297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355102 RingCT/type: yes/0
Extra: 01a9648d25fc0acca319e9ece4d96213b913f48e9bf843110275afea966f257e6202110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.652953931000 dcy

stealth address amount amount idx
00: 8a579ea8b4ba6ad3b460434ae12741dfb92350a232e5957c4ae99e8a82eef523 0.652953931000 1353672 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": 897307, "vin": [ { "gen": { "height": 897297 } } ], "vout": [ { "amount": 652953931, "target": { "key": "8a579ea8b4ba6ad3b460434ae12741dfb92350a232e5957c4ae99e8a82eef523" } } ], "extra": [ 1, 169, 100, 141, 37, 252, 10, 204, 163, 25, 233, 236, 228, 217, 98, 19, 185, 19, 244, 142, 155, 248, 67, 17, 2, 117, 175, 234, 150, 111, 37, 126, 98, 2, 17, 0, 0, 0, 11, 250, 243, 92, 156, 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