← previous blocknext block →recent activity
Analyzing
Block #112,594,014
10 transactions · 10 stateful · 2026-10-11 22:59:17 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,594,014 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xfa4630d4…3846
0x34b655…2a6f
4 touches
1 conflict
0x364161de…acf4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 conflicts
0x5492de24…e2e8
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity