← previous blocknext block →recent activity
Analyzing
Block #98,735,793
27 transactions · 24 stateful · 2026-08-24 10:37:04 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,735,793 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w08w19w010w111w012w013w114w216w317w418w522w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0001
0x659bd0…a9da
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x54907f2c…4a40
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: 0xbb3f3cb7…74e046
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity