← previous blocknext block →recent activity
Analyzing
Block #102,743,615
13 transactions · 13 stateful · 2026-09-07 11:36:15 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,743,615 · 13 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
2w03w04w15w16w17w08w29w110w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x7d63d93a…1188
0x34b655…2a6f
4 touches
1 conflict
0x834128b8…1616
0x34b655…2a6f
4 touches
1 conflict
0x96ed54e2…04ed
0x34b655…2a6f
4 touches
1 conflict
0xacd43549…94f9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xccdcfcbc…c7a0
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: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity