← previous blocknext block →recent activity
Analyzing
Block #102,358,665
26 transactions · 24 stateful · 2026-09-06 03:09:40 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,358,665 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w116w017w120w221w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb007c532…74ee
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xb007c532cf…6074ee
Audit this contract →
← previous block·next block →recent activity