← previous blocknext block →recent activity
Analyzing
Block #106,198,413
19 transactions · 16 stateful · 2026-09-19 14:15:35 UTC
Parallelism
79/100
Blocked
19%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,198,413 · 19 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
2w06w18w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbca3b8a9…8af1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0x634015e1…0b09
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x7eb3ae1e…a1a3
0x34b655…2a6f
4 touches
1 conflict
0x88fc2a68…3918
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
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 0xbca3b8a97e…938af1
Audit this contract →
← previous block·next block →recent activity