← previous blocknext block →recent activity
Analyzing
Block #98,925,313
29 transactions · 23 stateful · 2026-08-25 02:30:52 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,925,313 · 29 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
3w06w17w08w19w011w012w113w120w224w125w226w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x4c812cd5…b6a3
0x40c49f…2af0
6 touches
3 conflicts
0xe49b1b9b…0be1
0x2b46c0…1669
4 touches
1 conflict
0x110a3804…f842
0x34b655…2a6f
4 touches
1 conflict
0x251861eb…78fd
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity