← previous blocknext block →recent activity
Analyzing
Block #102,207,314
26 transactions · 25 stateful · 2026-09-05 14:22:47 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,207,314 · 26 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
1w02w13w05w06w17w28w312w113w418w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0xdf409966…6b16
0x3bd359…433a
6 touches
3 conflicts
0x5b0621ee…3c2c
0x284f45…7777
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x00000000…0004
0x7aed55…0617
6 touches
3 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
5 touches
3 conflicts
0x152f8e3d…3da0
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: 0xf5b5f7f8…a36d70
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity