← previous blocknext block →recent activity
Analyzing
Block #98,388,355
12 transactions · 12 stateful · 2026-08-23 04:52:51 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,388,355 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa006091f…8027
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x338437ea…9c59
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x92bb4e9d…0f03
0x34b655…2a6f
4 touches
1 conflict
0x3ebcb88d…be9e
0x34b655…2a6f
2 touches
0 conflicts
0x6aaf9040…5a24
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 0xa006091ffb…a68027
Audit this contract →
← previous block·next block →recent activity