← previous blocknext block →recent activity
Analyzing
Block #98,671,366
20 transactions · 20 stateful · 2026-08-24 05:08:23 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,671,366 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w09w111w012w113w214w216w318w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ef66342…e727
0x34b655…2a6f
8 touches
6 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5273be82…485e
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x2ef66342f4…05e727
Audit this contract →
← previous block·next block →recent activity