← previous blocknext block →recent activity
Analyzing
Block #74,787,890
14 transactions · 12 stateful · 2026-05-15 16:31:40 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,787,890 · 14 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7867a0c…4c51
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0xd1a96708…b985
0xd32edf…ff58
3 touches
1 conflict
0x17a5f99d…d30b
0x065c9d…c394
2 touches
0 conflicts
0x7069fe05…581f
0x065c9d…c394
2 touches
0 conflicts
0x9b6962e4…7e41
0x065c9d…c394
2 touches
0 conflicts
0xafc586fc…6243
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 0xa7867a0ceb…034c51
Audit this contract →
← previous block·next block →recent activity