← previous blocknext block →recent activity
Analyzing
Block #90,947,123
8 transactions · 7 stateful · 2026-07-28 03:11:01 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,947,123 · 8 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
0xdd87e0b7…a6d3
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14b3c0c8…9736
0x34b655…2a6f
2 touches
0 conflicts
0x2210c4e2…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x2549796f…83dd
0x34b655…2a6f
2 touches
0 conflicts
0x3377da70…01e5
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
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 0xdd87e0b7f4…15a6d3
Audit this contract →
← previous block·next block →recent activity