← previous blocknext block →recent activity
Analyzing
Block #100,094,757
22 transactions · 19 stateful · 2026-08-29 04:57:23 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,094,757 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w29w312w113w414w216w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99210cfe…f780
0x34b655…2a6f
10 touches
10 conflicts
0x61571888…b392
0x34b655…2a6f
10 touches
10 conflicts
0x8675c5dc…6f28
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0xef471e49…ee97
0x40c49f…2af0
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 0x99210cfe0c…0df780
Audit this contract →
← previous block·next block →recent activity