← previous blocknext block →recent activity
Analyzing
Block #90,679,503
19 transactions · 18 stateful · 2026-07-27 04:44:35 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,679,503 · 19 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
2w03w16w07w08w010w111w213w214w215w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x9608485c…1507
0x34b655…2a6f
6 touches
3 conflicts
0x2cc85280…c2f7
0x34b655…2a6f
4 touches
1 conflict
0x6077cb2d…4806
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity