← previous blocknext block →recent activity
Analyzing
Block #99,180,963
25 transactions · 24 stateful · 2026-08-26 00:03:47 UTC
Parallelism
92/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,180,963 · 25 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
5w06w07w112w013w115w118w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f3ee473…7ccb
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xe9410c19…a5a4
0x34b655…2a6f
4 touches
1 conflict
0x3364609c…a7b6
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x72dc4eca…50dd
0x065c9d…c394
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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
1 conflict on slot 0x6f3ee473ce…e47ccb
Audit this contract →
← previous block·next block →recent activity