← previous blocknext block →recent activity
Analyzing
Block #99,247,475
13 transactions · 10 stateful · 2026-08-26 05:38:26 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,247,475 · 13 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
4w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6358ca8…39c0
0x34b655…2a6f
4 touches
1 conflict
0xc1a4c088…e828
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18b9bf34…31af
0x065c9d…c394
2 touches
0 conflicts
0x9f2e09a6…d6b8
0x065c9d…c394
2 touches
0 conflicts
0xbdd568a5…cebd
0x065c9d…c394
2 touches
0 conflicts
0xdee3b829…1ec0
0x065c9d…c394
2 touches
0 conflicts
0xdfe56835…9972
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 0xb6358ca855…4a39c0
Audit this contract →
← previous block·next block →recent activity