← previous blocknext block →recent activity
Analyzing
Block #73,674,441
14 transactions · 12 stateful · 2026-05-10 12:36:03 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,674,441 · 14 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
4w06w17w28w39w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xd1907261…cbf3
0x065c9d…c394
4 touches
1 conflict
0xf3f2ed04…7135
0x065c9d…c394
3 touches
1 conflict
0xde9ef06b…596d
0x065c9d…c394
3 touches
1 conflict
0xe96873ba…cfa3
0x065c9d…c394
3 touches
1 conflict
0x79f4f8ea…5ab8
0x065c9d…c394
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity