← previous blocknext block →recent activity
Analyzing
Block #90,819,063
11 transactions · 11 stateful · 2026-07-27 16:26:47 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,819,063 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf359a948…0f6c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0xfb0022d6…1264
0x34b655…2a6f
4 touches
1 conflict
0x6b346db8…48fd
0x34b655…2a6f
4 touches
1 conflict
0x7bc81c3e…54a2
0x34b655…2a6f
4 touches
1 conflict
0x6c7cb3c8…71da
0x34b655…2a6f
4 touches
1 conflict
0xda5c5025…caae
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 0xf359a94846…170f6c
Audit this contract →
← previous block·next block →recent activity