← previous blocknext block →recent activity
Analyzing
Block #79,241,211
19 transactions · 16 stateful · 2026-06-05 07:33:59 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,241,211 · 19 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
3w04w06w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xb2910607…2667
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x014dc312…7787
0xd32edf…ff58
3 touches
1 conflict
0x01e1b563…ace5
0x065c9d…c394
3 touches
1 conflict
0x6ff8a7f4…932e
0x065c9d…c394
3 touches
1 conflict
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 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity