← previous blocknext block →recent activity
Analyzing
Block #98,754,623
21 transactions · 19 stateful · 2026-08-24 12:11:52 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,754,623 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w010w111w213w314w415w116w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffdec3e3…614c
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
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: 0x40c49f17…d22af0
10 conflicts on slot 0xffdec3e3f5…5f614c
Audit this contract →
← previous block·next block →recent activity