← previous blocknext block →recent activity
Analyzing
Block #98,073,268
16 transactions · 12 stateful · 2026-08-22 02:26:53 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,073,268 · 16 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
6w012w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56ae218…1fc5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x166e9860…6947
0x34b655…2a6f
2 touches
0 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
2 touches
0 conflicts
0x5b1375e0…c01d
0x34b655…2a6f
2 touches
0 conflicts
0x7a4bab36…0169
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 0xa56ae21853…e31fc5
Audit this contract →
← previous block·next block →recent activity