← previous blocknext block →recent activity
Analyzing
Block #98,063,916
30 transactions · 25 stateful · 2026-08-22 01:39:49 UTC
Parallelism
87/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,063,916 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w010w114w015w117w220w021w222w323w224w125w327w028w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x198cd812…4111
0x34b655…2a6f
4 touches
1 conflict
0x28f0ff48…9443
0x34b655…2a6f
4 touches
1 conflict
0x29cd05f5…390c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity