← previous blocknext block →recent activity
Analyzing
Block #99,947,821
23 transactions · 21 stateful · 2026-08-28 16:37:32 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,947,821 · 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
1w02w13w24w27w08w19w210w312w213w314w118w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbe956fc6…6523
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5684aadd…8d62
0x34b655…2a6f
6 touches
3 conflicts
0x18aae231…0b41
0x065c9d…c394
5 touches
3 conflicts
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xb17bd0ad…56d0
0x34b655…2a6f
4 touches
1 conflict
0xf139a55f…2854
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity