← previous blocknext block →recent activity
Analyzing
Block #98,671,927
21 transactions · 19 stateful · 2026-08-24 05:11:18 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,671,927 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w39w012w113w214w418w019w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity