← previous blocknext block →recent activity
Analyzing
Block #112,486,029
10 transactions · 9 stateful · 2026-10-11 13:55:58 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,486,029 · 10 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0xdad20621…06b1
0x34b655…2a6f
4 touches
1 conflict
0xe6085598…2849
0x34b655…2a6f
4 touches
1 conflict
0xa5ab7b8a…c97b
0x34b655…2a6f
4 touches
1 conflict
0x2ae2b5fd…1e43
0x34b655…2a6f
2 touches
0 conflicts
0x35eab2e5…3c0a
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x92b24e8a…1afa
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 0xd58e5c6b09…577188
Audit this contract →
← previous block·next block →recent activity