← previous blocknext block →recent activity
Analyzing
Block #106,184,605
28 transactions · 26 stateful · 2026-09-19 13:06:06 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,184,605 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w28w09w010w011w112w213w314w315w419w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78f38373…89fb
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0xad553998…3167
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
8 touches
6 conflicts
0xd597209e…9800
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdb0f2d37…bebb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x78f3837317…2289fb
Audit this contract →
← previous block·next block →recent activity