← previous blocknext block →recent activity
Analyzing
Block #106,189,887
20 transactions · 16 stateful · 2026-09-19 13:32:41 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,189,887 · 20 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
1w02w03w08w19w210w112w216w017w118w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708d7a74…09e3
0x34b655…2a6f
8 touches
6 conflicts
0x82ce020f…352c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xda6f06b7…34db
0x34b655…2a6f
4 touches
1 conflict
0xe99c1230…1f9b
0x34b655…2a6f
4 touches
1 conflict
0xfda729a6…3a4e
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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 0x708d7a74a7…5d09e3
Audit this contract →
← previous block·next block →recent activity