← previous blocknext block →recent activity
Analyzing
Block #102,683,416
12 transactions · 12 stateful · 2026-09-07 06:33:22 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,683,416 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6db9cc…cd4b
0x34b655…2a6f
4 touches
1 conflict
0x26c599c1…706c
0x34b655…2a6f
4 touches
1 conflict
0x38874c5d…0912
0x34b655…2a6f
4 touches
1 conflict
0x3c577f09…4ed2
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x5158bba9…dddb
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
0x34b655…2a6f
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
1 conflict on slot 0x0a6db9cc05…ebcd4b
Audit this contract →
← previous block·next block →recent activity