← previous blocknext block →recent activity
Analyzing
Block #75,516,903
29 transactions · 20 stateful · 2026-05-19 01:48:19 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,516,903 · 29 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
1w02w13w26w213w014w315w019w125w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xf8480e2a…dfef
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity