← previous blocknext block →recent activity
Analyzing
Block #102,058,051
24 transactions · 23 stateful · 2026-09-05 01:45:58 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,058,051 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w17w28w39w414w215w016w317w118w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
6 touches
3 conflicts
0xe22677a3…304f
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x6f232437…749d
0x34b655…2a6f
4 touches
1 conflict
0x703249c2…e321
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity