← previous blocknext block →recent activity
Analyzing
Block #90,573,145
12 transactions · 12 stateful · 2026-07-26 19:49:31 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,573,145 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa969f55…8bd7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd33a109e…bdb6
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xf7019ae9…bfb0
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5a
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
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 0xfa969f55d0…138bd7
Audit this contract →
← previous block·next block →recent activity