← previous blocknext block →recent activity
Analyzing
Block #90,453,110
8 transactions · 8 stateful · 2026-07-26 09:45:41 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,453,110 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0xa922e7e3…7214
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0xf55a3b7e…c720
0x34b655…2a6f
3 touches
1 conflict
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x08803a9b…dfbd
0x34b655…2a6f
2 touches
0 conflicts
0x1683d146…5ec2
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
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 0x5b37bb6bbf…0aaaff
Audit this contract →
← previous block·next block →recent activity