Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4e4ee3cd720b0a1cc560a584d4ea8e90fc33ec1e350f200300a54b98e3dc80

Tx prefix hash: 4e636b6edf757c0eae1e3773616b80cdd113ea094f0e77a32b5fde1c55ecc50b
Tx public key: 2876fd7657608a82f81c66ae2e5c1ac7d6d1bdec22b6a318555206de9479b797
Timestamp: 1657994537 Timestamp [UCT]: 2022-07-16 18:02:17 Age [y:d:h:m:s]: 02:244:18:30:04
Block: 545169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696101 RingCT/type: yes/0
Extra: 012876fd7657608a82f81c66ae2e5c1ac7d6d1bdec22b6a318555206de9479b7970211000000022e6b1fd5000000000000000000

1 output(s) for total of 9.585812546000 dcy

stealth address amount amount idx
00: 0c7efc00cf67eb477cabbb6f73b4ae06bbd2ce62487d6fc1428831a2ea141a94 9.585812546000 976032 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": 545179, "vin": [ { "gen": { "height": 545169 } } ], "vout": [ { "amount": 9585812546, "target": { "key": "0c7efc00cf67eb477cabbb6f73b4ae06bbd2ce62487d6fc1428831a2ea141a94" } } ], "extra": [ 1, 40, 118, 253, 118, 87, 96, 138, 130, 248, 28, 102, 174, 46, 92, 26, 199, 214, 209, 189, 236, 34, 182, 163, 24, 85, 82, 6, 222, 148, 121, 183, 151, 2, 17, 0, 0, 0, 2, 46, 107, 31, 213, 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