← previous blocknext block →recent activity
Analyzing
Block #98,019,781
27 transactions · 26 stateful · 2026-08-21 21:57:35 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,019,781 · 27 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
1w03w04w15w06w09w210w011w115w016w317w122w023w124w225w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0xf11c72ff…11b5
0x40c49f…2af0
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x2d536b5d…ea41
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x01b1d217…3693
0x065c9d…c394
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