← previous blocknext block →recent activity
Analyzing
Block #99,316,170
14 transactions · 13 stateful · 2026-08-26 11:24:05 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,316,170 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9421a154…d296
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0x5cc58846…f744
0x065c9d…c394
2 touches
0 conflicts
0x8b151cb4…a5e1
0x065c9d…c394
2 touches
0 conflicts
0xfd69847b…7ff0
0x065c9d…c394
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 0x9421a154a7…5bd296
Audit this contract →
← previous block·next block →recent activity