← previous blocknext block →recent activity
Analyzing
Block #90,690,730
7 transactions · 7 stateful · 2026-07-27 05:41:04 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,690,730 · 7 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
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0xaa9f27b0…9cf2
0x34b655…2a6f
4 touches
1 conflict
0x9608485c…1507
0x34b655…2a6f
4 touches
1 conflict
0x1980d4f3…175f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x27f0a7e4…ccd7
0x34b655…2a6f
2 touches
0 conflicts
0x363a4317…87d2
0x34b655…2a6f
2 touches
0 conflicts
0x366c7d57…0ed1
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 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity