← previous blocknext block →recent activity
Analyzing
Block #71,688,961
7 transactions · 6 stateful · 2026-05-01 08:04:48 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,688,961 · 7 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xbefde765…6384
0x065c9d…c394
4 touches
1 conflict
0x738b60d0…3f25
0x065c9d…c394
4 touches
1 conflict
0x59f864cf…d79b
0x065c9d…c394
3 touches
1 conflict
0x3ed439ea…ccc8
0x065c9d…c394
3 touches
1 conflict
0x798ac4e4…8d57
0x065c9d…c394
2 touches
0 conflicts
0xbc70d921…d885
0x065c9d…c394
2 touches
0 conflicts
0xd74d5bed…5e7e
0x2a68ba…90c5
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity