← previous blocknext block →recent activity
Analyzing
Block #98,439,758
13 transactions · 11 stateful · 2026-08-23 09:11:28 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,439,758 · 13 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
2w03w07w18w09w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
4 touches
1 conflict
0x62406c85…e348
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42e917f7…ed8c
0x34b655…2a6f
2 touches
0 conflicts
0xac0b4a08…faae
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 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity