← previous blocknext block →recent activity
Analyzing
Block #90,791,821
24 transactions · 19 stateful · 2026-07-27 14:09:38 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,791,821 · 24 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
5w06w17w08w19w010w014w117w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0xaa9f27b0…9cf2
0x34b655…2a6f
4 touches
1 conflict
0x9608485c…1507
0x34b655…2a6f
4 touches
1 conflict
0x3e30f1bf…6453
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d1be9fc…7e20
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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity