← previous blocknext block →recent activity
Analyzing
Block #74,024,470
8 transactions · 6 stateful · 2026-05-12 03:40:40 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,024,470 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x47fdf0fa…22c3
0x065c9d…c394
2 touches
0 conflicts
0x5a7494a0…7ba9
0x065c9d…c394
2 touches
0 conflicts
0xa939938c…4572
0x09475a…400f
2 touches
0 conflicts
0x00000000…0000
0x48aa78…9cb3
2 touches
0 conflicts
0x24325fdd…053f
0xd5d960…eaee
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity