← previous blocknext block →recent activity
Analyzing
Block #90,993,269
16 transactions · 15 stateful · 2026-07-28 07:03:19 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,993,269 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3b27440d…f9f0
0x34b655…2a6f
6 touches
3 conflicts
0xd8675136…9a01
0x34b655…2a6f
6 touches
3 conflicts
0xae28870c…072f
0x34b655…2a6f
6 touches
3 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x3830f5a7…34ad
0x34b655…2a6f
4 touches
1 conflict
0x3e4af36e…07ae
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity