← previous blocknext block →recent activity
Analyzing
Block #98,017,208
28 transactions · 21 stateful · 2026-08-21 21:44:38 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,017,208 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w09w010w111w018w019w121w223w124w326w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b4267f7…96c0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afaa
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x641245e3…6323
0xc8689a…ee79
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
3 conflicts on slot 0x0b4267f73f…2796c0
Audit this contract →
← previous block·next block →recent activity