← previous blocknext block →recent activity
Analyzing
Block #91,410,394
30 transactions · 25 stateful · 2026-07-29 18:03:53 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,410,394 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w210w311w413w014w015w116w219w520w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0008
0x0ea966…0742
10 touches
10 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
10 touches
10 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
10 touches
10 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
10 touches
10 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
8 touches
6 conflicts
0xc014bcf3…3ac7
0x34b655…2a6f
6 touches
3 conflicts
0x3a8eba5b…53c3
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity