← previous blocknext block →recent activity
Analyzing
Block #90,918,883
28 transactions · 22 stateful · 2026-07-28 00:48:58 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,918,883 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w09w110w211w312w413w014w115w016w119w221w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x152f8e3d…3da0
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity