← previous blocknext block →recent activity
Analyzing
Block #99,883,937
30 transactions · 23 stateful · 2026-08-28 11:15:34 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,883,937 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w07w011w013w114w115w116w221w323w125w226w427w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0a8fcf75…c69b
0x34b655…2a6f
4 touches
1 conflict
0x1fd4b21e…febb
0x34b655…2a6f
4 touches
1 conflict
0xadce6355…03bf
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity