← previous blocknext block →recent activity
Analyzing
Block #74,258,112
11 transactions · 9 stateful · 2026-05-13 05:34:42 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,258,112 · 11 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5baad89f…7256
0x065c9d…c394
4 touches
1 conflict
0xb50ada9a…6cb7
0x065c9d…c394
3 touches
1 conflict
0xbaa28b23…0402
0x065c9d…c394
3 touches
1 conflict
0x7eb9ffaf…a284
0x065c9d…c394
2 touches
0 conflicts
0xa15e10cf…972b
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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