← previous blocknext block →recent activity
Analyzing
Block #106,801,999
19 transactions · 18 stateful · 2026-09-21 16:54:27 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
2.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,801,999 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w110w312w413w314w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f5d7ccd…83d4
0x34b655…2a6f
14 touches
21 conflicts
0x151d8039…827a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe2bb444d…6190
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xabf57eb6…416d
0x34b655…2a6f
8 touches
6 conflicts
0xac42991e…5438
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
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
21 conflicts on slot 0x6f5d7ccdbe…db83d4
Audit this contract →
← previous block·next block →recent activity