← previous blocknext block →recent activity
Analyzing
Block #98,025,898
26 transactions · 23 stateful · 2026-08-21 22:28:31 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,025,898 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w010w011w112w113w216w017w120w123w124w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0xe9e92bac…00ed
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity