← previous blocknext block →recent activity
Analyzing
Block #102,524,033
12 transactions · 12 stateful · 2026-09-06 17:07:40 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,524,033 · 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x811723dc…307e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x16d77246…bac5
0x34b655…2a6f
2 touches
0 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
2 touches
0 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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 0x811723dc92…b0307e
Audit this contract →
← previous block·next block →recent activity