← previous blocknext block →recent activity
Analyzing
Block #100,751,783
17 transactions · 17 stateful · 2026-08-31 12:07:12 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,751,783 · 17 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
1w02w03w14w05w16w09w110w212w315w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8622d89e…7b47
0x34b655…2a6f
10 touches
10 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0x279d4414…f732
0x34b655…2a6f
4 touches
1 conflict
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70e677f5…e3bd
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
10 conflicts on slot 0x8622d89ec8…547b47
Audit this contract →
← previous block·next block →recent activity