← previous blocknext block →recent activity
Analyzing
Block #106,188,804
20 transactions · 16 stateful · 2026-09-19 13:27:14 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,188,804 · 20 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
15w016w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9ddc6d5…86a2
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0xd41f5136…97c6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x2965e2d6…5800
0x34b655…2a6f
2 touches
0 conflicts
0x5371eb8f…845b
0x34b655…2a6f
2 touches
0 conflicts
0x65903ef9…2567
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 0xd9ddc6d597…8d86a2
Audit this contract →
← previous block·next block →recent activity