← previous blocknext block →recent activity
Analyzing
Block #74,238,368
8 transactions · 6 stateful · 2026-05-13 03:23:31 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,238,368 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
2 touches
0 conflicts
0x1348a4c0…8d18
0x34b655…2a6f
2 touches
0 conflicts
0x1348a4c0…8d19
0x34b655…2a6f
2 touches
0 conflicts
0x71e4ffd1…9beb
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 0x5d70606abb…6e1d53
Audit this contract →
← previous block·next block →recent activity