← previous blocknext block →recent activity
Analyzing
Block #102,473,838
28 transactions · 25 stateful · 2026-09-06 12:52:59 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,473,838 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w17w110w011w115w016w117w018w119w020w121w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x288b6dbc…e879
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
4 touches
1 conflict
0x6662d004…f56b
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
3 conflicts on slot 0x6ca0994e1e…7002ef
Audit this contract →
← previous block·next block →recent activity