← previous blocknext block →recent activity
Analyzing
Block #112,083,158
15 transactions · 15 stateful · 2026-10-10 04:09:06 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,083,158 · 15 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100ec7e6…6b5a
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0x2f8f905b…5e0b
0x34b655…2a6f
4 touches
1 conflict
0x6211d1cf…e687
0x34b655…2a6f
4 touches
1 conflict
0x6515cd4a…d383
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xc5f336ca…912e
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
6 conflicts on slot 0x100ec7e671…ee6b5a
Audit this contract →
← previous block·next block →recent activity