← previous blocknext block →recent activity
Analyzing
Block #99,778,559
25 transactions · 21 stateful · 2026-08-28 02:22:41 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,778,559 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w08w111w014w115w016w118w220w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd1e92f08…d3ba
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity