← previous blocknext block →recent activity
Analyzing
Block #98,424,772
17 transactions · 17 stateful · 2026-08-23 07:56:04 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,424,772 · 17 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
4w05w06w18w211w312w114w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2b78ba10…9ce5
0x34b655…2a6f
4 touches
1 conflict
0x358bde2d…0586
0x34b655…2a6f
4 touches
1 conflict
0x42c0a5d3…a476
0x34b655…2a6f
4 touches
1 conflict
0x746c5510…9e98
0x34b655…2a6f
4 touches
1 conflict
0x8c2196f7…a156
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity