← previous blocknext block →recent activity
Analyzing
Block #112,484,692
21 transactions · 20 stateful · 2026-10-11 13:49:14 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,484,692 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w112w014w115w016w117w118w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1011ef4d…634d
0x34b655…2a6f
4 touches
1 conflict
0x3f5c1ed2…9bee
0x34b655…2a6f
4 touches
1 conflict
0x49fe70fa…3c13
0x34b655…2a6f
4 touches
1 conflict
0x53057a6c…ce62
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x72179448…92dd
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x9c0e4c97…e395
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
1 conflict on slot 0x1011ef4dae…a6634d
Audit this contract →
← previous block·next block →recent activity