← previous blocknext block →recent activity
Analyzing
Block #74,896,475
23 transactions · 16 stateful · 2026-05-16 04:35:50 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,896,475 · 23 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
1w02w15w06w213w016w017w118w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
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