← previous blocknext block →recent activity
Analyzing
Block #98,089,781
18 transactions · 17 stateful · 2026-08-22 03:49:59 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,089,781 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w06w09w111w012w114w015w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe62e1553…ed4b
0x34b655…2a6f
4 touches
1 conflict
0xe7082461…6b63
0x34b655…2a6f
4 touches
1 conflict
0xed5ae65a…3635
0x34b655…2a6f
4 touches
1 conflict
0xf4866d2c…0b69
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xe251ba03…50f8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity