← previous blocknext block →recent activity
Analyzing
Block #112,103,842
13 transactions · 9 stateful · 2026-10-10 05:53:10 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,103,842 · 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
6w07w18w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d971bc9…fadc
0x34b655…2a6f
4 touches
1 conflict
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x4d971bc9…fadd
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xd02fcc08…ee5a
0x34b655…2a6f
4 touches
1 conflict
0xd7e6493c…5ee8
0x34b655…2a6f
4 touches
1 conflict
0x8f7ca305…2923
0x34b655…2a6f
3 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 0x4d971bc9ee…5efadc
Audit this contract →
← previous block·next block →recent activity