← previous blocknext block →recent activity
Analyzing
Block #76,256,190
13 transactions · 10 stateful · 2026-05-22 11:56:37 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,256,190 · 13 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x101d9c90…ec70
0x065c9d…c394
4 touches
1 conflict
0x064aba9b…ed0f
0x065c9d…c394
3 touches
1 conflict
0x0c754c8a…245c
0x065c9d…c394
3 touches
1 conflict
0x1fa11f78…1bc7
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x96db9c58…9494
0x065c9d…c394
2 touches
0 conflicts
0xaff21b49…c09b
0x065c9d…c394
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 0x22e0cc1d4a…90ad04
Audit this contract →
← previous block·next block →recent activity