← previous blocknext block →recent activity
Analyzing
Block #102,641,806
8 transactions · 8 stateful · 2026-09-07 03:04:02 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,641,806 · 8 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
1w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x347817fd…9a4e
0x34b655…2a6f
4 touches
1 conflict
0x18860aca…0f33
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0xb59ce75e…0cc7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity