← previous blocknext block →recent activity
Analyzing
Block #75,789,308
12 transactions · 9 stateful · 2026-05-20 08:05:03 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,789,308 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf30c163…0fb6
0x34b655…2a6f
4 touches
1 conflict
0x50e10826…843b
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0xc009105d…96f7
0x8d66a4…3095
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x4337fa38…e7fb
0x34b655…2a6f
2 touches
0 conflicts
0x54c7b292…c151
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: Perpl
1 conflict on slot 0xaf30c16357…c70fb6
Audit this contract →
← previous block·next block →recent activity