Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d1420e37b45bd580bd9fa9d2c1ec4ce297d7f657e656908454cb7fe8cbbda4

Tx prefix hash: f08d8de8394fcd5dd97b018dbb614b198815d0e24bf4fa0c289dff97a1700513
Tx public key: 58d80a8745628ce79a40cc1f5b93a5a8b51fd0e83465b481a33f701b7d7cc084
Timestamp: 1582987888 Timestamp [UCT]: 2020-02-29 14:51:28 Age [y:d:h:m:s]: 05:249:13:29:30
Block: 74205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1330339 RingCT/type: yes/0
Extra: 0158d80a8745628ce79a40cc1f5b93a5a8b51fd0e83465b481a33f701b7d7cc0840211000000170aca7173000000000000000000

1 output(s) for total of 348.440661435000 dcy

stealth address amount amount idx
00: 0707af3046522efddfe4456d496a3af68d8daa3dcbc2ac7a1b29d659788b7b57 348.440661435000 137188 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": 74215, "vin": [ { "gen": { "height": 74205 } } ], "vout": [ { "amount": 348440661435, "target": { "key": "0707af3046522efddfe4456d496a3af68d8daa3dcbc2ac7a1b29d659788b7b57" } } ], "extra": [ 1, 88, 216, 10, 135, 69, 98, 140, 231, 154, 64, 204, 31, 91, 147, 165, 168, 181, 31, 208, 232, 52, 101, 180, 129, 163, 63, 112, 27, 125, 124, 192, 132, 2, 17, 0, 0, 0, 23, 10, 202, 113, 115, 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