← previous blocknext block →recent activity
Analyzing
Block #90,643,213
12 transactions · 12 stateful · 2026-07-27 01:42:01 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,643,213 · 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
1w02w13w24w37w48w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f68ff96…38a6
0x34b655…2a6f
6 touches
3 conflicts
0xea817351…30e4
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcbe863a2…b2dd
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x488e5288…7823
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
3 conflicts on slot 0x2f68ff96e7…b538a6
Audit this contract →
← previous block·next block →recent activity