← previous blocknext block →recent activity
Analyzing
Block #90,839,770
12 transactions · 11 stateful · 2026-07-27 18:10:57 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,839,770 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427dec7f…61c6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc3fc40da…1c60
0x34b655…2a6f
6 touches
3 conflicts
0x3a072a7c…581c
0x34b655…2a6f
4 touches
1 conflict
0x487f23db…38b6
0x34b655…2a6f
4 touches
1 conflict
0x663ab2c3…67ab
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6ae4a85e…c097
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 0x427dec7fbc…3e61c6
Audit this contract →
← previous block·next block →recent activity