← previous blocknext block →recent activity
Analyzing
Block #90,642,510
16 transactions · 13 stateful · 2026-07-27 01:38:29 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,642,510 · 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
1w02w16w07w18w29w310w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b329d79…f248
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x6b329d7951…5ef248
Audit this contract →
← previous block·next block →recent activity