Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a42afa059d2fef5a8a7dd10de745388ef84ad6118f1a1b8c875e4818e15fdcc3

Tx prefix hash: 387b29d20af6597a7c6f6162e182064fa9b64fdbdc2fe709cad6e191285b9f55
Tx public key: cdc03a1d51fcffbe29a1cf742592a1555f140cc5cc4aa7dfb4505d8903cfdf57
Timestamp: 1673612433 Timestamp [UCT]: 2023-01-13 12:20:33 Age [y:d:h:m:s]: 02:299:05:49:29
Block: 673832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733268 RingCT/type: yes/0
Extra: 01cdc03a1d51fcffbe29a1cf742592a1555f140cc5cc4aa7dfb4505d8903cfdf5702110000000175e3f0e9000000000000000000

1 output(s) for total of 3.591822070000 dcy

stealth address amount amount idx
00: 305155a65cca4f5975b57968e1ce47302441d4703b1b5d01e44968dbe1946fcb 3.591822070000 1115461 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": 673842, "vin": [ { "gen": { "height": 673832 } } ], "vout": [ { "amount": 3591822070, "target": { "key": "305155a65cca4f5975b57968e1ce47302441d4703b1b5d01e44968dbe1946fcb" } } ], "extra": [ 1, 205, 192, 58, 29, 81, 252, 255, 190, 41, 161, 207, 116, 37, 146, 161, 85, 95, 20, 12, 197, 204, 74, 167, 223, 180, 80, 93, 137, 3, 207, 223, 87, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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