← previous blocknext block →recent activity
Analyzing
Block #73,416,914
8 transactions · 7 stateful · 2026-05-09 07:58:32 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,416,914 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdcc9fbc0…989c
0x065c9d…c394
3 touches
1 conflict
0x1bc9d89b…aad6
0x065c9d…c394
3 touches
1 conflict
0x2e81835d…d789
0x065c9d…c394
2 touches
0 conflicts
0x56b3c9c7…7783
0x065c9d…c394
2 touches
0 conflicts
0x5bfd2e59…4fde
0x065c9d…c394
2 touches
0 conflicts
0x6cf038fa…5403
0x065c9d…c394
2 touches
0 conflicts
0x6d2c25b4…5ae8
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity