Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2fd232068d5b27936464ab22a194d6fedd8414d304ba52822cf79a5e6636a7

Tx prefix hash: 9f09318ddcd2fa99d3de2a13057368ddb4fd84ccfe6090edac7c7aeaeea35dec
Tx public key: 59b2c638d4ad2ffa7bd1600284bfb540af45a20ebb8bff2e3dd34993f4a5f598
Timestamp: 1583457151 Timestamp [UCT]: 2020-03-06 01:12:31 Age [y:d:h:m:s]: 04:336:03:44:37
Block: 77197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134500 RingCT/type: yes/0
Extra: 0159b2c638d4ad2ffa7bd1600284bfb540af45a20ebb8bff2e3dd34993f4a5f5980211000000020aca7173000000000000000000

1 output(s) for total of 340.576820737000 dcy

stealth address amount amount idx
00: 7a046d56fb36672b7f3c63362b7b7c9279aa56185f0a2b1af2d839aab69c13c4 340.576820737000 142080 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": 77207, "vin": [ { "gen": { "height": 77197 } } ], "vout": [ { "amount": 340576820737, "target": { "key": "7a046d56fb36672b7f3c63362b7b7c9279aa56185f0a2b1af2d839aab69c13c4" } } ], "extra": [ 1, 89, 178, 198, 56, 212, 173, 47, 250, 123, 209, 96, 2, 132, 191, 181, 64, 175, 69, 162, 14, 187, 139, 255, 46, 61, 211, 73, 147, 244, 165, 245, 152, 2, 17, 0, 0, 0, 2, 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