← previous blocknext block →recent activity
Analyzing
Block #91,410,417
25 transactions · 20 stateful · 2026-07-29 18:04:00 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,410,417 · 25 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
1w02w13w24w310w011w112w215w017w119w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x3fcc24d4…fa74
0x851145…3f07
4 touches
1 conflict
0x80a745fc…ce9e
0x851145…3f07
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity