← previous blocknext block →recent activity
Analyzing
Block #98,389,278
15 transactions · 13 stateful · 2026-08-23 04:57:30 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,389,278 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0xebe4afed…ea8d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x342e1a0c…21dc
0x34b655…2a6f
2 touches
0 conflicts
0x51fc8795…1266
0x34b655…2a6f
2 touches
0 conflicts
0x6719a767…9d62
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xb5f5f77567…50010b
Audit this contract →
← previous block·next block →recent activity