← previous blocknext block →recent activity
Analyzing
Block #74,312,042
17 transactions · 14 stateful · 2026-05-13 11:33:31 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,312,042 · 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
1w05w012w113w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b28bf77…e53a
0x34b655…2a6f
4 touches
1 conflict
0xfb790f01…fea9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x75f6889e…7f1e
0x34b655…2a6f
4 touches
1 conflict
0x4f483049…3cc7
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x5a1fab28…8a82
0xd32edf…ff58
3 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: Perpl
1 conflict on slot 0x0b28bf777b…5ce53a
Audit this contract →
← previous block·next block →recent activity