← previous blocknext block →recent activity
Analyzing
Block #103,213,360
24 transactions · 22 stateful · 2026-09-09 03:05:25 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,213,360 · 24 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
5w06w17w215w321w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x11339529…5f52
0x065c9d…c394
3 touches
1 conflict
0xb0d00094…efb6
0x065c9d…c394
3 touches
1 conflict
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity