← previous blocknext block →recent activity
Analyzing
Block #98,928,779
22 transactions · 21 stateful · 2026-08-25 02:48:18 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,928,779 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w39w310w012w013w414w117w018w119w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd984a5e4…5cfc
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity