← previous blocknext block →recent activity
Analyzing
Block #90,948,963
6 transactions · 6 stateful · 2026-07-28 03:20:16 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,948,963 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x646278ac…2ebf
0x34b655…2a6f
4 touches
1 conflict
0x7b481037…3457
0x34b655…2a6f
4 touches
1 conflict
0x5692e125…1727
0x34b655…2a6f
4 touches
1 conflict
0x86fc5a37…81eb
0x34b655…2a6f
4 touches
1 conflict
0x13aac2b2…9642
0x34b655…2a6f
2 touches
0 conflicts
0x1de6e314…2416
0x34b655…2a6f
2 touches
0 conflicts
0x1fc736a3…9b67
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x646278acb4…9e2ebf
Audit this contract →
← previous block·next block →recent activity