← previous blocknext block →recent activity
Analyzing
Block #99,369,099
16 transactions · 13 stateful · 2026-08-26 15:50:38 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,369,099 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w09w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5c5dffb4…0ab4
0x851145…3f07
4 touches
1 conflict
0x99b29f97…d502
0x851145…3f07
4 touches
1 conflict
0xd9438fc3…f9a2
0x851145…3f07
4 touches
1 conflict
0x057ac2ab…4010
0x188d58…ea8e
2 touches
0 conflicts
0x10f0a1bf…12c3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf8e6479f3b…bbf193
Audit this contract →
← previous block·next block →recent activity