← previous blocknext block →recent activity
Analyzing
Block #103,041,045
17 transactions · 14 stateful · 2026-09-08 12:36:41 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,041,045 · 17 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
1w010w011w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e1625ee…1c63
0x065c9d…c394
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf11d5d9b…a5a2
0x065c9d…c394
3 touches
1 conflict
0xd663e37e…8a1c
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x50474c48…cddb
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 0x2e1625eec5…271c63
Audit this contract →
← previous block·next block →recent activity