← previous blocknext block →recent activity
Analyzing
Block #98,507,642
30 transactions · 27 stateful · 2026-08-23 14:54:52 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,507,642 · 30 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
2w03w17w08w09w110w212w013w015w116w317w418w120w121w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x3c2892bf…9a20
0x34b655…2a6f
8 touches
6 conflicts
0x81189ce4…12c6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x3d8c0e3e…2aad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x7462b8f2…6312
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity