← previous blocknext block →recent activity
Analyzing
Block #112,243,937
13 transactions · 10 stateful · 2026-10-10 17:37:58 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,243,937 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf96fd6ab…2f90
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x53057a6c…ce62
0x34b655…2a6f
4 touches
1 conflict
0x002597f4…646c
0x34b655…2a6f
4 touches
1 conflict
0x2dd724a3…3121
0x34b655…2a6f
2 touches
0 conflicts
0x3a81fd48…f064
0x34b655…2a6f
2 touches
0 conflicts
0x565326bb…ae7e
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
0x34b655…2a6f
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
1 conflict on slot 0xf96fd6ab64…112f90
Audit this contract →
← previous block·next block →recent activity