← previous blocknext block →recent activity
Analyzing
Block #98,568,488
13 transactions · 11 stateful · 2026-08-23 20:12:36 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,568,488 · 13 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
2w06w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x2bea5ce8…3c07
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd97b0449…00a0
0x34b655…2a6f
4 touches
1 conflict
0x70cd98d6…54bd
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0xa92fc25f…0349
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity