← previous blocknext block →recent activity
Analyzing
Block #90,636,069
8 transactions · 8 stateful · 2026-07-27 01:06:05 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,636,069 · 8 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
1w02w03w14w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec152baf…a069
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
0x34b655…2a6f
2 touches
0 conflicts
0x6396a4c4…f626
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 0xec152baf75…11a069
Audit this contract →
← previous block·next block →recent activity