← previous blocknext block →recent activity
Analyzing
Block #94,667,774
15 transactions · 14 stateful · 2026-08-10 03:26:26 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,667,774 · 15 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
2w06w07w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed6d5e8f…b410
0x34b655…2a6f
4 touches
1 conflict
0x32ae718c…1437
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
2 touches
0 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xed6d5e8f80…f9b410
Audit this contract →
← previous block·next block →recent activity