← previous blocknext block →recent activity
Analyzing
Block #112,478,763
21 transactions · 18 stateful · 2026-10-11 13:19:25 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,478,763 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x23755a5e…c027
0x34b655…2a6f
8 touches
6 conflicts
0x17100566…8efd
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x3cb01fa7…835e
0x34b655…2a6f
4 touches
1 conflict
0x4ec3c3a5…735d
0x34b655…2a6f
4 touches
1 conflict
0x68055fa2…229e
0x34b655…2a6f
4 touches
1 conflict
0x97096d9a…e280
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity