← previous blocknext block →recent activity
Analyzing
Block #112,231,121
17 transactions · 16 stateful · 2026-10-10 16:33:29 UTC
Parallelism
76/100
Blocked
19%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,231,121 · 17 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
13w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc4550172…3d03
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xa3f09358…6cde
0x34b655…2a6f
4 touches
1 conflict
0xcc69885f…792f
0x30a88b…7102
2 touches
0 conflicts
0xd5d6c8dc…8045
0x30a88b…7102
2 touches
0 conflicts
0xd9d16d34…330f
0x30a88b…7102
2 touches
0 conflicts
0xdc686ec4…237e
0x30a88b…7102
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