← previous blocknext block →recent activity
Analyzing
Block #104,916,147
32 transactions · 25 stateful · 2026-09-15 02:39:29 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,916,147 · 32 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
4w05w19w213w015w016w117w118w219w325w430w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x79fcd4be…8bfb
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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