← previous blocknext block →recent activity
Analyzing
Block #98,419,857
21 transactions · 18 stateful · 2026-08-23 07:31:20 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,419,857 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w314w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e39dec3…c8e8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9660902a…a12b
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x57b4bb61…6d23
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x6b602543…32e5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x9e39dec393…6dc8e8
Audit this contract →
← previous block·next block →recent activity