← previous blocknext block →recent activity
Analyzing
Block #98,675,033
15 transactions · 14 stateful · 2026-08-24 05:27:26 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,675,033 · 15 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
1w02w03w14w07w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7feb1ae…2a5a
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0xd7feb1ae0a…5a2a5a
Audit this contract →
← previous block·next block →recent activity