← previous blocknext block →recent activity
Analyzing
Block #90,818,714
18 transactions · 18 stateful · 2026-07-27 16:25:01 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,818,714 · 18 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xbb38a037…5349
0x34b655…2a6f
4 touches
1 conflict
0x1c9916f0…5e75
0x34b655…2a6f
2 touches
0 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
2 touches
0 conflicts
0x2d327a2e…cbff
0x34b655…2a6f
2 touches
0 conflicts
0x2dee2876…b255
0x34b655…2a6f
2 touches
0 conflicts
0x3e0065ad…e39b
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity