← previous blocknext block →recent activity
Analyzing
Block #90,891,464
31 transactions · 30 stateful · 2026-07-27 22:31:02 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,891,464 · 31 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
1w04w05w16w07w19w123w224w225w329w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefeb7be7…ae9a
0x34b655…2a6f
6 touches
3 conflicts
0xa3834f05…a4cf
0x34b655…2a6f
6 touches
3 conflicts
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x475bdffd…9a36
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54ff4977…6281
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0xefeb7be71c…27ae9a
Audit this contract →
← previous block·next block →recent activity