← previous blocknext block →recent activity
Analyzing
Block #99,619,404
37 transactions · 34 stateful · 2026-08-27 12:57:11 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.22
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,619,404 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w08w19w010w111w214w015w016w117w118w220w321w022w124w425w526w427w429w535w836w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
10 touches
10 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity