← previous blocknext block →recent activity
Analyzing
Block #91,406,360
17 transactions · 16 stateful · 2026-07-29 17:43:26 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,406,360 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w19w010w111w213w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d38e3ab…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
6 touches
3 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 conflicts
0xd98b3c10…67b8
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
3 conflicts on slot 0x0d38e3ab0f…4da8f6
Audit this contract →
← previous block·next block →recent activity