← previous blocknext block →recent activity
Analyzing
Block #74,421,438
16 transactions · 13 stateful · 2026-05-13 23:41:16 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,421,438 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w110w212w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
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: 0xfdc9ea59…b68789
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity