← previous blocknext block →recent activity
Analyzing
Block #91,411,020
44 transactions · 38 stateful · 2026-07-29 18:07:03 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
1.84
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,411,020 · 44 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
2w03w14w25w36w47w58w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0008
0x0ea966…0742
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
10 touches
10 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
10 touches
10 conflicts
0xe5bb3628…e5f1
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: 0x48cba278…e2b48b
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity