← previous blocknext block →recent activity
Analyzing
Block #98,849,365
26 transactions · 25 stateful · 2026-08-24 20:08:47 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,849,365 · 26 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
3w04w17w08w09w110w211w314w115w018w120w223w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0x7b7bcac3…8fbf
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: 0xbb3f3cb7…74e046
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity