← previous blocknext block →recent activity
Analyzing
Block #108,286,363
15 transactions · 12 stateful · 2026-09-26 21:28:05 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,286,363 · 15 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
1w02w03w14w16w07w210w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf575e041…43f4
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x81955a0a…29ee
0xc9d9fa…20f2
4 touches
1 conflict
0x00000000…0003
0x125f12…a50b
4 touches
1 conflict
0x00000000…0007
0xc35b1c…298f
4 touches
1 conflict
0x00000000…000a
0xc35b1c…298f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x589beebf…422d
0x34b655…2a6f
4 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
3 conflicts on slot 0xf575e041e6…6d43f4
Audit this contract →
← previous block·next block →recent activity