← previous blocknext block →recent activity
Analyzing
Block #81,836,140
14 transactions · 11 stateful · 2026-06-17 08:05:50 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,836,140 · 14 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
1w02w17w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e27b0f9…22d0
0x065c9d…c394
4 touches
1 conflict
0x4ce48890…98ad
0x065c9d…c394
4 touches
1 conflict
0xd2b4580b…e56c
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xb922a263…e100
0x065c9d…c394
2 touches
0 conflicts
0xc41ae364…920b
0x065c9d…c394
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 0x9e27b0f93e…1e22d0
Audit this contract →
← previous block·next block →recent activity