← previous blocknext block →recent activity
Analyzing
Block #99,867,817
23 transactions · 21 stateful · 2026-08-28 09:54:22 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,867,817 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w19w211w312w413w514w615w316w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49d6800f…40eb
0x34b655…2a6f
8 touches
6 conflicts
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0x93ffcd76…894e
0x34b655…2a6f
6 touches
3 conflicts
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x17b028d3…4150
0x34b655…2a6f
4 touches
1 conflict
0x7b803988…15e2
0x34b655…2a6f
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
6 conflicts on slot 0x49d6800ff5…3a40eb
Audit this contract →
← previous block·next block →recent activity