← previous blocknext block →recent activity
Analyzing
Block #73,979,162
16 transactions · 15 stateful · 2026-05-11 22:37:06 UTC
Parallelism
25/100
Blocked
73%
Avg conflicts / tx
4.13
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,979,162 · 16 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24cfe713…0f91
0x25d593…7777
24 touches
66 conflicts
0x00000000…0000
0x30611e…d8d9
24 touches
66 conflicts
0x00000000…0001
0x30611e…d8d9
24 touches
66 conflicts
0x00000000…0003
0x30611e…d8d9
24 touches
66 conflicts
0xe3ee7f9e…f356
0x3bd359…433a
24 touches
66 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x070a562a…8147
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
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: SPIDERMON (SPIDERMON)
66 conflicts on slot 0x24cfe713e3…6c0f91
Audit this contract →
← previous block·next block →recent activity