← previous blocknext block →recent activity
Analyzing
Block #74,901,861
8 transactions · 8 stateful · 2026-05-16 05:11:48 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,901,861 · 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd76eace3…6b4d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x4acce2d3…daf6
0x065c9d…c394
3 touches
1 conflict
0x7b8ae145…4cae
0x065c9d…c394
3 touches
1 conflict
0x046d48e9…0c5d
0x065c9d…c394
2 touches
0 conflicts
0x51616fab…e066
0x065c9d…c394
2 touches
0 conflicts
0xe8b3ac1a…8303
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
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 0xd76eace315…876b4d
Audit this contract →
← previous block·next block →recent activity