← previous blocknext block →recent activity
Analyzing
Block #98,742,867
29 transactions · 21 stateful · 2026-08-24 11:12:39 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,742,867 · 29 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
1w06w09w110w011w012w113w015w119w223w325w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x16339c3a…53d2
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity