← previous blocknext block →recent activity
Analyzing
Block #90,949,061
16 transactions · 16 stateful · 2026-07-28 03:20:46 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,949,061 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xb566e26f…6d5d
0x34b655…2a6f
4 touches
1 conflict
0x00ae9786…7fca
0x065c9d…c394
2 touches
0 conflicts
0x1ed17d86…3a4b
0x065c9d…c394
2 touches
0 conflicts
0x72b10177…b12b
0x065c9d…c394
2 touches
0 conflicts
0x83ea7073…fc6c
0x065c9d…c394
2 touches
0 conflicts
0x9e70cc41…d8d8
0x065c9d…c394
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity