← previous blocknext block →recent activity
Analyzing
Block #74,765,567
17 transactions · 11 stateful · 2026-05-15 14:02:19 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,765,567 · 17 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
1w02w18w014w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7cee1be1…e770
0x34b655…2a6f
3 touches
1 conflict
0xc976c824…170b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x116e7d…d8f1
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
2 touches
0 conflicts
0xab2f6eed…254c
0x188d58…ea8e
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 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity