← previous blocknext block →recent activity
Analyzing
Block #74,631,462
6 transactions · 6 stateful · 2026-05-14 23:07:06 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,631,462 · 6 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xf7110a5b…db42
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x10afac92…dcbd
0x1c921c…0f5b
2 touches
0 conflicts
0x21d5695a…a023
0x1c921c…0f5b
2 touches
0 conflicts
0x2569078d…1c40
0x1c921c…0f5b
2 touches
0 conflicts
0x23114fac…630a
0x34b655…2a6f
2 touches
0 conflicts
0x2d5e3771…9a87
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 0xfe3d37ee7e…836e67
Audit this contract →
← previous block·next block →recent activity