← previous blocknext block →recent activity
Analyzing
Block #100,612,117
21 transactions · 21 stateful · 2026-08-31 00:24:39 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,612,117 · 21 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
1w02w03w14w05w16w27w38w013w414w015w116w118w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xa987699f…eabe
0x2b46c0…1669
4 touches
1 conflict
0xea7ebe9d…709e
0x2b46c0…1669
4 touches
1 conflict
0x15698ac9…2a46
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity