← previous blocknext block →recent activity
Analyzing
Block #90,437,949
7 transactions · 7 stateful · 2026-07-26 08:28:54 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,437,949 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c7eac39…f34d
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0fce4497…fc71
0x34b655…2a6f
2 touches
0 conflicts
0x316b255f…4dc7
0x34b655…2a6f
2 touches
0 conflicts
0x3d430410…a9ca
0x34b655…2a6f
2 touches
0 conflicts
0x4b32d24f…0428
0x34b655…2a6f
2 touches
0 conflicts
0x4ba7b9b3…7583
0x34b655…2a6f
2 touches
0 conflicts
0x53f7214d…8ec6
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 0x8c7eac397b…15f34d
Audit this contract →
← previous block·next block →recent activity