← previous blocknext block →recent activity
Analyzing
Block #75,543,268
18 transactions · 13 stateful · 2026-05-19 04:45:23 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,543,268 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xff140c5a…7bfe
0x34b655…2a6f
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xc289d22f…7a26
0x065c9d…c394
3 touches
1 conflict
0x486ec532…b04a
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0xa17ec269…7cdd
0x1d1325…2305
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: Perpl
3 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity