← previous blocknext block →recent activity
Analyzing
Block #108,467,062
15 transactions · 14 stateful · 2026-09-27 12:37:29 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,467,062 · 15 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
3w04w05w16w07w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0c7deec4…77cb
0x34b655…2a6f
2 touches
0 conflicts
0x1e9a3fc4…c4e1
0x34b655…2a6f
2 touches
0 conflicts
0x27944231…c5ff
0x34b655…2a6f
2 touches
0 conflicts
0x456c43b2…eb47
0x34b655…2a6f
2 touches
0 conflicts
0x615bb18e…cd47
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity