← previous blocknext block →recent activity
Analyzing
Block #102,205,065
22 transactions · 19 stateful · 2026-09-05 14:11:25 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,205,065 · 22 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
2w03w14w05w26w09w116w117w218w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x29316387…6612
0x34b655…2a6f
4 touches
1 conflict
0xd868fb65…3b4a
0xe1c8b7…3022
4 touches
1 conflict
0x5b0621ee…3c2c
0x284f45…7777
4 touches
1 conflict
0xdf409966…6b16
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x7aed55…0617
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: Perpl
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity