← previous blocknext block →recent activity
Analyzing
Block #112,235,661
10 transactions · 10 stateful · 2026-10-10 16:56:20 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,235,661 · 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0xd8936bb8…e417
0xf42df8…ad97
4 touches
1 conflict
0x5ed7be90…e66b
0x34b655…2a6f
4 touches
1 conflict
0x5eef3cee…c1f4
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xd8936bb8…e417
0x80ef19…40df
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity