← previous blocknext block →recent activity
Analyzing
Block #106,207,414
12 transactions · 12 stateful · 2026-09-19 15:00:56 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,207,414 · 12 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
2w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8b0f947e…578f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0145aa28…106b
0x34b655…2a6f
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x18a2605a…6e7f
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity