← previous blocknext block →recent activity
Analyzing
Block #91,248,277
23 transactions · 22 stateful · 2026-07-29 04:26:58 UTC
Parallelism
83/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,248,277 · 23 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
13w014w118w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x539ac47f…eb6f
0x34b655…2a6f
4 touches
1 conflict
0x5a08ca7f…6546
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0x539ac47ff9…e9eb6f
Audit this contract →
← previous block·next block →recent activity