← previous blocknext block →recent activity
Analyzing
Block #98,927,215
28 transactions · 26 stateful · 2026-08-25 02:40:26 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,927,215 · 28 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
2w04w05w06w17w28w19w114w015w117w018w019w120w126w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cff6b80…47a8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47d
0x1b6862…e19c
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
3 conflicts on slot 0x4cff6b805d…b147a8
Audit this contract →
← previous block·next block →recent activity