← previous blocknext block →recent activity
Analyzing
Block #112,243,945
27 transactions · 20 stateful · 2026-10-10 17:38:00 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,243,945 · 27 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
1w02w13w04w05w16w27w315w016w118w019w123w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4550172…3d03
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc506e687…19b5
0x34b655…2a6f
6 touches
3 conflicts
0x9026bdfc…b5a7
0x34b655…2a6f
4 touches
1 conflict
0xa36afdbf…9917
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
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 0xc4550172b5…c13d03
Audit this contract →
← previous block·next block →recent activity