← previous blocknext block →recent activity
Analyzing
Block #105,619,280
19 transactions · 14 stateful · 2026-09-17 13:38:23 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,619,280 · 19 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xff52cb10…6a9c
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity