← previous blocknext block →recent activity
Analyzing
Block #90,810,625
16 transactions · 15 stateful · 2026-07-27 15:44:17 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,810,625 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w410w514w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb515f271…1a26
0x34b655…2a6f
4 touches
1 conflict
0xc3b532be…7ce3
0x34b655…2a6f
4 touches
1 conflict
0xcf8e8419…c691
0x34b655…2a6f
4 touches
1 conflict
0xd7db3988…5b15
0x34b655…2a6f
4 touches
1 conflict
0x1b244003…c9cf
0x34b655…2a6f
4 touches
1 conflict
0x1b244003…c9d0
0x34b655…2a6f
4 touches
1 conflict
0xafe72ad3…c5fa
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity