← previous blocknext block →recent activity
Analyzing
Block #98,321,350
23 transactions · 22 stateful · 2026-08-22 23:15:47 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,321,350 · 23 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
2w03w14w05w19w010w111w112w214w315w316w018w022w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b16dd0…0426
0x34b655…2a6f
8 touches
6 conflicts
0xb63ef486…0dcc
0x34b655…2a6f
6 touches
3 conflicts
0xadb553c0…430a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7db78f05…2895
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0xb7b16dd022…c80426
Audit this contract →
← previous block·next block →recent activity