← previous blocknext block →recent activity
Analyzing
Block #106,272,677
9 transactions · 9 stateful · 2026-09-19 20:29:26 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,272,677 · 9 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x784f870c…0bfb
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 conflicts
0x2f50c84a…3640
0x34b655…2a6f
2 touches
0 conflicts
0x656c2ba5…d35b
0x34b655…2a6f
2 touches
0 conflicts
0x7499cc33…a306
0x34b655…2a6f
2 touches
0 conflicts
0x75f36d60…8556
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 0x784f870cd3…370bfb
Audit this contract →
← previous block·next block →recent activity