← previous blocknext block →recent activity
Analyzing
Block #100,021,480
24 transactions · 24 stateful · 2026-08-28 22:48:31 UTC
Parallelism
54/100
Blocked
63%
Avg conflicts / tx
2.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,021,480 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w612w713w814w915w1017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67779a11…82f8
0x350035…7777
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd97b0449…00a0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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: 0x35003555…c27777
55 conflicts on slot 0x67779a1196…f282f8
Audit this contract →
← previous block·next block →recent activity