← previous blocknext block →recent activity
Analyzing
Block #98,017,223
13 transactions · 13 stateful · 2026-08-21 21:44:43 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,017,223 · 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
1w02w05w16w07w08w212w1
- 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
0xdf352747…7eaf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x47425794…9157
0x34b655…2a6f
4 touches
1 conflict
0x8aa11acb…4a40
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
3 conflicts on slot 0x0b4267f73f…2796c0
Audit this contract →
← previous block·next block →recent activity