Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f2426b3f71884a087a11ea4ff2176d65a5cd9ef61d034d36764b06d0ee0172

Tx prefix hash: b0d1014990c6f7a4a88d8a5b9f4817d489dcc30a7a59190a83bf7f780dd49527
Tx public key: a135f44c41cd8f72c2bd1c9974d1907a9cd998839b6a9289122425ef942d2760
Timestamp: 1732906522 Timestamp [UCT]: 2024-11-29 18:55:22 Age [y:d:h:m:s]: 00:122:15:18:29
Block: 1164464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87439 RingCT/type: yes/0
Extra: 01a135f44c41cd8f72c2bd1c9974d1907a9cd998839b6a9289122425ef942d27600211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21e317600f1ad8b0d35c3792de77880de7167fce72aec503bd4f7d08bfdfd90 0.600000000000 1650137 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": 1164474, "vin": [ { "gen": { "height": 1164464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21e317600f1ad8b0d35c3792de77880de7167fce72aec503bd4f7d08bfdfd90" } } ], "extra": [ 1, 161, 53, 244, 76, 65, 205, 143, 114, 194, 189, 28, 153, 116, 209, 144, 122, 156, 217, 152, 131, 155, 106, 146, 137, 18, 36, 37, 239, 148, 45, 39, 96, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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