← previous blocknext block →recent activity
Analyzing
Block #74,332,442
25 transactions · 16 stateful · 2026-05-13 13:49:07 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,332,442 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w210w313w014w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c5811ce…dfd8
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaa3492db…3703
0x34b655…2a6f
6 touches
3 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
6 touches
3 conflicts
0x7b50a82b…f53d
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 0x0c5811ce53…f7dfd8
Audit this contract →
← previous block·next block →recent activity