← previous blocknext block →recent activity
Analyzing
Block #105,470,383
17 transactions · 16 stateful · 2026-09-17 01:08:59 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,470,383 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w111w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0050
0x80c745…7210
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x11007f8e…a9fe
0x851145…3f07
3 touches
1 conflict
0x98552cba…5e9a
0x065c9d…c394
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity