← previous blocknext block →recent activity
Analyzing
Block #90,430,199
7 transactions · 6 stateful · 2026-07-26 07:49:03 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,430,199 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xdaf33a71…3bf9
0x34b655…2a6f
4 touches
1 conflict
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x0a6c31fc…f4c3
0x34b655…2a6f
2 touches
0 conflicts
0x15a30412…1a64
0x34b655…2a6f
2 touches
0 conflicts
0x160c630d…90ce
0x34b655…2a6f
2 touches
0 conflicts
0x2848aeee…60ee
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 0x939cdd567e…a300c8
Audit this contract →
← previous block·next block →recent activity