← previous blocknext block →recent activity
Analyzing
Block #98,926,419
28 transactions · 22 stateful · 2026-08-25 02:36:26 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,926,419 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w214w015w117w218w320w324w025w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x3439deb5…2fa4
0x40c49f…2af0
8 touches
6 conflicts
0xa5f71148…62ee
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00fbbe4d…1277
0x40c49f…2af0
5 touches
3 conflicts
0x2f74f175…9287
0x2b46c0…1669
4 touches
1 conflict
0x6eff310a…c34c
0x2b46c0…1669
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