← previous blocknext block →recent activity
Analyzing
Block #98,840,410
26 transactions · 24 stateful · 2026-08-24 19:23:44 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,840,410 · 26 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
5w06w17w28w39w010w011w112w213w314w015w417w018w121w022w123w124w125w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd984a5e4…5cfc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x085df2c1…305a
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 0xd984a5e4e9…3a5cfc
Audit this contract →
← previous block·next block →recent activity