← previous blocknext block →recent activity
Analyzing
Block #102,104,375
13 transactions · 13 stateful · 2026-09-05 05:41:01 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,104,375 · 13 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
3w05w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x3967a4c9…c000
0x34b655…2a6f
4 touches
1 conflict
0x522f84c3…6901
0x065c9d…c394
2 touches
0 conflicts
0xbe9b5442…46ea
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x4f125e8922…507ee0
Audit this contract →
← previous block·next block →recent activity