Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85786248dc508f7ac2d126bed698e37264469662caa810d0ee58805f1a08073

Tx prefix hash: bc2b1c4842b3516fdc6c5cc78f7478dceefb91ffd0f927b205e967923e590fa5
Tx public key: bd0d5f015b9f635ae62373f6843ea5a2c35b1f05869e7c1f8d4760f773163f7c
Timestamp: 1582488501 Timestamp [UCT]: 2020-02-23 20:08:21 Age [y:d:h:m:s]: 05:260:19:26:23
Block: 70964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337488 RingCT/type: yes/0
Extra: 01bd0d5f015b9f635ae62373f6843ea5a2c35b1f05869e7c1f8d4760f773163f7c0211000000238a2ee0d9000000000000000000

1 output(s) for total of 357.176295376000 dcy

stealth address amount amount idx
00: a14390623500a408821732a84dcf54ddf191452ec54dd9aa481b4fc9ed9f0302 357.176295376000 131167 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": 70974, "vin": [ { "gen": { "height": 70964 } } ], "vout": [ { "amount": 357176295376, "target": { "key": "a14390623500a408821732a84dcf54ddf191452ec54dd9aa481b4fc9ed9f0302" } } ], "extra": [ 1, 189, 13, 95, 1, 91, 159, 99, 90, 230, 35, 115, 246, 132, 62, 165, 162, 195, 91, 31, 5, 134, 158, 124, 31, 141, 71, 96, 247, 115, 22, 63, 124, 2, 17, 0, 0, 0, 35, 138, 46, 224, 217, 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