← previous blocknext block →recent activity
Analyzing
Block #112,611,798
16 transactions · 15 stateful · 2026-10-12 00:28:45 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,611,798 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62023181…811e
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0x6202318167…4d811e
Audit this contract →
← previous block·next block →recent activity