← previous blocknext block →recent activity
Analyzing
Block #102,862,210
23 transactions · 22 stateful · 2026-09-07 21:36:09 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,862,210 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w011w112w213w314w415w016w119w020w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x5d791d8d…93e1
0x851145…3f07
9 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity