← previous blocknext block →recent activity
Analyzing
Block #98,913,739
25 transactions · 21 stateful · 2026-08-25 01:32:38 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,913,739 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w09w114w015w116w218w220w021w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3c67d31e…3dbe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x768cffcd…2648
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity