← previous blocknext block →recent activity
Analyzing
Block #100,147,526
16 transactions · 15 stateful · 2026-08-29 09:23:13 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,147,526 · 16 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
1w02w15w07w18w012w213w114w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58658217…80ff
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x327c57dd…836d
0x34b655…2a6f
6 touches
3 conflicts
0xec85b41e…7c95
0x1b6862…e19c
4 touches
1 conflict
0x191e0467…70e5
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
6 conflicts on slot 0x5865821757…9680ff
Audit this contract →
← previous block·next block →recent activity