← previous blocknext block →recent activity
Analyzing
Block #100,585,833
22 transactions · 19 stateful · 2026-08-30 22:12:25 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,585,833 · 22 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
4w05w16w07w18w09w110w211w212w315w116w217w118w320w021w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda3b445…e5c1
0x34b655…2a6f
6 touches
3 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
0xd7443f37…eb79
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
3 conflicts on slot 0xfda3b4456b…f8e5c1
Audit this contract →
← previous block·next block →recent activity