← previous blocknext block →recent activity
Analyzing
Block #102,745,178
16 transactions · 14 stateful · 2026-09-07 11:44:07 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,745,178 · 16 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
2w03w04w15w110w211w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0facab3e…e7df
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfaf5fe80…1ffc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2f454d61…0807
0x065c9d…c394
3 touches
1 conflict
0x1358f3cc…722c
0x065c9d…c394
3 touches
1 conflict
0x51aa664e…d3b8
0x34b655…2a6f
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 0x0facab3e15…90e7df
Audit this contract →
← previous block·next block →recent activity