← previous blocknext block →recent activity
Analyzing
Block #99,457,662
9 transactions · 9 stateful · 2026-08-26 23:16:33 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,457,662 · 9 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10c583e4…57d4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c67a605…19c4
0x065c9d…c394
2 touches
0 conflicts
0x56f36365…7c40
0x065c9d…c394
2 touches
0 conflicts
0x9253b625…0de6
0x065c9d…c394
2 touches
0 conflicts
0xa1866d38…6081
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 0x10c583e444…e557d4
Audit this contract →
← previous block·next block →recent activity