← previous blocknext block →recent activity
Analyzing
Block #99,480,903
28 transactions · 27 stateful · 2026-08-27 01:13:35 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,480,903 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w08w19w210w211w313w116w418w520w621w722w125w527w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b4edd58…9623
0x34b655…2a6f
14 touches
21 conflicts
0x904e2bfb…1544
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x896fd276…3a6f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd814f518…f5b4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x6b4edd5859…d59623
Audit this contract →
← previous block·next block →recent activity