← previous blocknext block →recent activity
Analyzing
Block #98,985,286
14 transactions · 13 stateful · 2026-08-25 07:32:36 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,985,286 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39aafc65…aa29
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1adfc171…6f70
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe796f8b7…ad55
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0x39aafc6519…beaa29
Audit this contract →
← previous block·next block →recent activity