← previous blocknext block →recent activity
Analyzing
Block #112,319,853
25 transactions · 24 stateful · 2026-10-10 23:59:55 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,319,853 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xdd819920…1840
0x34b655…2a6f
4 touches
1 conflict
0x2aa8cd69…03b6
0xf42df8…ad97
4 touches
1 conflict
0x23fee964…ef41
0x34b655…2a6f
4 touches
1 conflict
0x4359639c…7bd3
0x34b655…2a6f
4 touches
1 conflict
0x2aa8cd69…03b6
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity