← previous blocknext block →recent activity
Analyzing
Block #98,644,137
37 transactions · 30 stateful · 2026-08-24 02:46:25 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,644,137 · 37 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
1w04w15w213w314w016w017w118w219w320w421w522w629w230w132w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x603ca7fe…3500
0xd32edf…ff58
5 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity