← previous blocknext block →recent activity
Analyzing
Block #74,610,419
19 transactions · 13 stateful · 2026-05-14 20:46:49 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,610,419 · 19 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
1w03w16w215w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0x59ef13ba…2741
0x34b655…2a6f
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x9e6962ea…42f1
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba62
0x188d58…ea8e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity