← previous blocknext block →recent activity
Analyzing
Block #101,966,194
14 transactions · 13 stateful · 2026-09-04 18:00:29 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,966,194 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0xa1623807…199e
0x34b655…2a6f
3 touches
1 conflict
0xb0e8e2d9…121d
0x34b655…2a6f
3 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x94789504…4524
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity