← previous blocknext block →recent activity
Analyzing
Block #98,661,857
16 transactions · 15 stateful · 2026-08-24 04:18:54 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,661,857 · 16 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
4w06w07w18w29w312w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0xe2ec3154…9a1d
0xa6afd3…d132
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x0bd5c557…de1e
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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