← previous blocknext block →recent activity
Analyzing
Block #102,446,695
24 transactions · 21 stateful · 2026-09-06 10:35:24 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,446,695 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w17w010w113w116w017w118w119w221w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x58b27dde…52d1
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe84da890…48ed
0x34b655…2a6f
4 touches
1 conflict
0xf7fa82d2…f00a
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: 0x80c74517…647210
1 conflict on slot 0x0000000000…00004f
Audit this contract →
← previous block·next block →recent activity