← previous blocknext block →recent activity
Analyzing
Block #98,741,208
23 transactions · 18 stateful · 2026-08-24 11:04:18 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,741,208 · 23 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
1w03w15w06w17w08w19w210w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x9fe76a0a…8a11
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0x3c83a6e4…25bc
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
1 conflict on slot 0x1db5837f6b…d01264
Audit this contract →
← previous block·next block →recent activity