← previous blocknext block →recent activity
Analyzing
Block #100,585,670
23 transactions · 22 stateful · 2026-08-30 22:11:36 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,585,670 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w110w011w212w313w414w515w618w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7443f37…eb79
0x34b655…2a6f
12 touches
15 conflicts
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0xf74a7e74…ef2b
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0xbce23dad…a8c0
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x54c8c0a4…812a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xd7443f3786…61eb79
Audit this contract →
← previous block·next block →recent activity