← previous blocknext block →recent activity
Analyzing
Block #106,356,538
31 transactions · 24 stateful · 2026-09-20 03:31:27 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,356,538 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w09w110w011w112w213w216w322w023w125w226w229w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
10 touches
10 conflicts
0xbbbc5cf2…d2db
0x34b655…2a6f
8 touches
6 conflicts
0x347160f5…0d1c
0x34b655…2a6f
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x554bc428…1432
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
0x34b655…2a6f
6 touches
3 conflicts
0x750aafb0…01e9
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity