← previous blocknext block →recent activity
Analyzing
Block #99,667,752
20 transactions · 18 stateful · 2026-08-27 17:01:21 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,667,752 · 20 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
5w07w011w012w113w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe226a0be…c046
0x34b655…2a6f
4 touches
1 conflict
0x137247ba…5992
0x34b655…2a6f
4 touches
1 conflict
0x4f001c53…fe42
0x34b655…2a6f
4 touches
1 conflict
0x60e5418d…038a
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xc0a73ae2…2e95
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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 0xe226a0be4d…4bc046
Audit this contract →
← previous block·next block →recent activity