← previous blocknext block →recent activity
Analyzing
Block #108,568,083
9 transactions · 9 stateful · 2026-09-27 21:06:13 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,568,083 · 9 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
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x031dfc88…2d44
0x065c9d…c394
3 touches
1 conflict
0x8cef77ee…fb67
0x065c9d…c394
3 touches
1 conflict
0xac8ac893…339b
0xd32edf…ff58
3 touches
1 conflict
0x4f2c4c3d…1ab9
0x065c9d…c394
2 touches
0 conflicts
0x86d9b05e…9646
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity