← previous blocknext block →recent activity
Analyzing
Block #90,881,090
6 transactions · 5 stateful · 2026-07-27 21:38:50 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,881,090 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x1eac6e74…32cd
0x34b655…2a6f
4 touches
1 conflict
0x258258fd…adc5
0x34b655…2a6f
2 touches
0 conflicts
0x278686dc…698d
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a04
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
2 touches
0 conflicts
0x2d327a2e…cbff
0x34b655…2a6f
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
1 conflict on slot 0x0d2e179149…08c1dd
Audit this contract →
← previous block·next block →recent activity