← previous blocknext block →recent activity
Analyzing
Block #106,308,087
11 transactions · 11 stateful · 2026-09-19 23:27:37 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,308,087 · 11 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
1w02w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0xd9b57567…1f3e
0x34b655…2a6f
6 touches
3 conflicts
0x7c2b0f0e…4933
0x34b655…2a6f
6 touches
3 conflicts
0x75f36d60…8556
0x34b655…2a6f
4 touches
1 conflict
0x8b7e5c4e…5fae
0x34b655…2a6f
4 touches
1 conflict
0x8cfa9962…2675
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
0x34b655…2a6f
4 touches
1 conflict
0xb322d117…905e
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
3 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity