← previous blocknext block →recent activity
Analyzing
Block #98,077,374
29 transactions · 25 stateful · 2026-08-22 02:47:32 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,077,374 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w09w115w116w218w219w321w022w123w225w326w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55192654…91fe
0x34b655…2a6f
4 touches
1 conflict
0x60726f3c…b5b8
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 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity