Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1be38e63a1a0df28fa6149c6d3d9685a6ab7a6d36d0a62cc21d60373005884

Tx prefix hash: c07294f00beed967e18b1cc6a2e458d1801e0f5c695cd901c203f96dec841841
Tx public key: 1f2caa95fc34b367aa20ecc350162ef5c1e7bebbb2ba0f2d83412a4717565556
Timestamp: 1700846983 Timestamp [UCT]: 2023-11-24 17:29:43 Age [y:d:h:m:s]: 01:164:18:20:04
Block: 898767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378940 RingCT/type: yes/0
Extra: 011f2caa95fc34b367aa20ecc350162ef5c1e7bebbb2ba0f2d83412a471756555602110000000133af99f4000000000000000000

1 output(s) for total of 0.645671799000 dcy

stealth address amount amount idx
00: ce6a9e9b3f6c83cb2c4e8bce6714b3c0c06423cb1c9ea77780f3258ff5cf69d8 0.645671799000 1355202 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": 898777, "vin": [ { "gen": { "height": 898767 } } ], "vout": [ { "amount": 645671799, "target": { "key": "ce6a9e9b3f6c83cb2c4e8bce6714b3c0c06423cb1c9ea77780f3258ff5cf69d8" } } ], "extra": [ 1, 31, 44, 170, 149, 252, 52, 179, 103, 170, 32, 236, 195, 80, 22, 46, 245, 193, 231, 190, 187, 178, 186, 15, 45, 131, 65, 42, 71, 23, 86, 85, 86, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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