Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1f9ec1cf96e6656abd757e40328cdaeb3bcabacee24fff50aff177b529c359

Tx prefix hash: b613ec0a0186dcad2e4fc969e515f5a3d95aecebaa1dc888c01876720beb7c30
Tx public key: 13bad9e2ab6a0a1c53d07a5d9b313857f40853523268afd1dc0c6ad0d47d7ca3
Timestamp: 1644789078 Timestamp [UCT]: 2022-02-13 21:51:18 Age [y:d:h:m:s]: 02:329:20:27:59
Block: 437995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755062 RingCT/type: yes/0
Extra: 0113bad9e2ab6a0a1c53d07a5d9b313857f40853523268afd1dc0c6ad0d47d7ca30211000000012e6b1fd5000000000000000000

1 output(s) for total of 21.716840373000 dcy

stealth address amount amount idx
00: 397ec36d96b26846fb86fe43773fcf0a61ac7059e5fa2aa922b647a07c4edd29 21.716840373000 849768 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": 438005, "vin": [ { "gen": { "height": 437995 } } ], "vout": [ { "amount": 21716840373, "target": { "key": "397ec36d96b26846fb86fe43773fcf0a61ac7059e5fa2aa922b647a07c4edd29" } } ], "extra": [ 1, 19, 186, 217, 226, 171, 106, 10, 28, 83, 208, 122, 93, 155, 49, 56, 87, 244, 8, 83, 82, 50, 104, 175, 209, 220, 12, 106, 208, 212, 125, 124, 163, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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