Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0559f8dc082554fde01d07475d07e83fdadfe77cdfe6ade21dc4fd6019d16c78

Tx prefix hash: e7d7d41b7aaf9c36fba19d4d48eb0f4d36926517803ef272ea1b31c24071beae
Tx public key: 20f7b5fa1299dd0775e364eec17a0f4e9b3c824286d825bceb1a21a9e14dd8c5
Timestamp: 1581904227 Timestamp [UCT]: 2020-02-17 01:50:27 Age [y:d:h:m:s]: 05:258:04:04:37
Block: 66386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1335350 RingCT/type: yes/0
Extra: 0120f7b5fa1299dd0775e364eec17a0f4e9b3c824286d825bceb1a21a9e14dd8c502110000000112c4732d000000000000000000

1 output(s) for total of 369.859205858000 dcy

stealth address amount amount idx
00: 93abd3bff352b7fd4be63ccbc5c017dd16da6f5d84f256200e3ddd92c594f271 369.859205858000 122309 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": 66396, "vin": [ { "gen": { "height": 66386 } } ], "vout": [ { "amount": 369859205858, "target": { "key": "93abd3bff352b7fd4be63ccbc5c017dd16da6f5d84f256200e3ddd92c594f271" } } ], "extra": [ 1, 32, 247, 181, 250, 18, 153, 221, 7, 117, 227, 100, 238, 193, 122, 15, 78, 155, 60, 130, 66, 134, 216, 37, 188, 235, 26, 33, 169, 225, 77, 216, 197, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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