← previous blocknext block →recent activity
Analyzing
Block #102,064,234
11 transactions · 10 stateful · 2026-09-05 02:17:18 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,064,234 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3167d7d8…a06b
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0xab3df58f…531b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd02ebff8…fe31
0x34b655…2a6f
4 touches
1 conflict
0xf139b130…d132
0x34b655…2a6f
3 touches
1 conflict
0x1c3c5667…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x33b7fbba…64de
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0x3167d7d865…e4a06b
Audit this contract →
← previous block·next block →recent activity