← previous blocknext block →recent activity
Analyzing
Block #74,331,988
24 transactions · 19 stateful · 2026-05-13 13:46:06 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,331,988 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w39w412w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xce288228…ef26
0x40c49f…2af0
4 touches
1 conflict
0x6a428b33…1053
0x754704…b603
4 touches
1 conflict
0xe5e8b071…f6de
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity