← previous blocknext block →recent activity
Analyzing
Block #98,065,496
21 transactions · 21 stateful · 2026-08-22 01:47:46 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,065,496 · 21 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
2w03w04w15w06w09w110w211w012w113w114w215w116w219w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3836a730…b3a9
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1fd77335…9120
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0xadbda1a7…5f21
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0x3836a73066…21b3a9
Audit this contract →
← previous block·next block →recent activity