← previous blocknext block →recent activity
Analyzing
Block #112,483,518
24 transactions · 22 stateful · 2026-10-11 13:43:20 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,483,518 · 24 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
5w08w19w211w015w016w118w119w221w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xb7b446d2…2006
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x471da687…7b29
0x34b655…2a6f
4 touches
1 conflict
0x4c94c9fc…e946
0x34b655…2a6f
4 touches
1 conflict
0x67cfcfc2…78dd
0x34b655…2a6f
4 touches
1 conflict
0x6ca8cf24…7151
0x34b655…2a6f
4 touches
1 conflict
0x8141fedc…d6c2
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity