← previous blocknext block →recent activity
Analyzing
Block #102,810,702
27 transactions · 25 stateful · 2026-09-07 17:16:54 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,810,702 · 27 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
1w02w15w06w17w214w015w118w019w122w023w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x06ce5d4b…c122
0x34ae4d…3fc5
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity