← previous blocknext block →recent activity
Analyzing
Block #99,820,677
17 transactions · 13 stateful · 2026-08-28 05:56:06 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,820,677 · 17 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
1w03w16w09w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x34e3cdd6…5645
0x34b655…2a6f
4 touches
1 conflict
0x5b50b454…614a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7a2adf2d…ad14
0x065c9d…c394
3 touches
1 conflict
0x68a23e3c…fbcd
0x065c9d…c394
3 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x670162a5…c01f
0x3bd359…433a
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 0x31d88d27c1…837617
Audit this contract →
← previous block·next block →recent activity