← previous blocknext block →recent activity
Analyzing
Block #104,916,212
25 transactions · 25 stateful · 2026-09-15 02:39:49 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,916,212 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w011w112w213w314w415w016w118w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97136bf4…a847
0x065c9d…c394
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0xc824469a…6425
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: Market-MON/USDC
10 conflicts on slot 0x97136bf480…56a847
Audit this contract →
← previous block·next block →recent activity