← previous blocknext block →recent activity
Analyzing
Block #74,331,913
35 transactions · 21 stateful · 2026-05-13 13:45:36 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,331,913 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w216w019w022w123w224w129w130w231w332w433w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x01737532…9b12
0x34b655…2a6f
6 touches
3 conflicts
0xa21e56c8…c63c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xe783dfa4…5494
0x1b6862…e19c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity