← previous blocknext block →recent activity
Analyzing
Block #98,734,664
24 transactions · 22 stateful · 2026-08-24 10:31:23 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,734,664 · 24 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
1w04w05w16w27w08w09w110w213w014w115w216w317w018w119w220w321w422w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd5e6c9d5…0455
0x40c49f…2af0
9 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
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