← previous blocknext block →recent activity
Analyzing
Block #106,224,403
21 transactions · 20 stateful · 2026-09-19 16:26:27 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,224,403 · 21 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
1w02w13w04w15w16w27w09w011w112w213w315w016w117w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0x93ef9802…ea80
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x638cd0f2…cb93
0x34b655…2a6f
6 touches
3 conflicts
0x7a1c8aca…40b1
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
6 conflicts on slot 0xa35509fa93…d55cb3
Audit this contract →
← previous block·next block →recent activity