← previous blocknext block →recent activity
Analyzing
Block #99,859,130
23 transactions · 23 stateful · 2026-08-28 09:10:35 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,859,130 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w18w010w111w012w113w214w316w418w019w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6325b483…af8a
0x34b655…2a6f
10 touches
10 conflicts
0x320d2876…56e5
0x34b655…2a6f
8 touches
6 conflicts
0xebe581d8…2696
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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
10 conflicts on slot 0x6325b48394…18af8a
Audit this contract →
← previous block·next block →recent activity