← previous blocknext block →recent activity
Analyzing
Block #100,125,315
10 transactions · 9 stateful · 2026-08-29 07:31:15 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,125,315 · 10 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
1w02w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a4f0eab…e28f
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e293
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e294
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e296
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e290
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x2a4f0eab9d…75e28f
Audit this contract →
← previous block·next block →recent activity