← previous blocknext block →recent activity
Analyzing
Block #74,427,633
25 transactions · 12 stateful · 2026-05-14 00:22:32 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,427,633 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w09w118w221w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xf226ece8…06de
0x065c9d…c394
4 touches
1 conflict
0x4db74a88…1c46
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity