← previous blocknext block →recent activity
Analyzing
Block #99,484,283
21 transactions · 18 stateful · 2026-08-27 01:30:37 UTC
Parallelism
90/100
Blocked
28%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,484,283 · 21 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
1w03w06w07w013w114w116w118w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08884f7c…c4d0
0x34b655…2a6f
4 touches
1 conflict
0x452799ab…27d4
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0xffc5c60b…6019
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0x08884f7c78…adc4d0
Audit this contract →
← previous block·next block →recent activity