← previous blocknext block →recent activity
Analyzing
Block #90,645,155
14 transactions · 13 stateful · 2026-07-27 01:51:47 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,645,155 · 14 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
2w03w18w210w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6396a4c4…f626
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x52e6b3e9…7ca6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x94e68337…5eb0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4228aa11…88fd
0x065c9d…c394
2 touches
0 conflicts
0x55bb363a…ace8
0x065c9d…c394
2 touches
0 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 0x6396a4c45b…5cf626
Audit this contract →
← previous block·next block →recent activity