← previous blocknext block →recent activity
Analyzing
Block #98,472,235
16 transactions · 15 stateful · 2026-08-23 11:55:13 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,472,235 · 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
3w09w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x999fd01c…deaa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2f0ac284…d044
0x34b655…2a6f
3 touches
1 conflict
0x472f52a5…39d3
0x34b655…2a6f
3 touches
1 conflict
0x79ce2c35…44f4
0x34b655…2a6f
2 touches
0 conflicts
0x8ff85b19…dde0
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 0x999fd01c6b…4ddeaa
Audit this contract →
← previous block·next block →recent activity