← previous blocknext block →recent activity
Analyzing
Block #103,210,570
20 transactions · 19 stateful · 2026-09-09 02:51:23 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,210,570 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w39w213w015w117w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf84a6…09e4
0x34b655…2a6f
8 touches
6 conflicts
0x24f88385…46c8
0x34b655…2a6f
6 touches
3 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x676707df…0e0a
0x34b655…2a6f
6 touches
3 conflicts
0x8478b6b5…eb3a
0x34b655…2a6f
6 touches
3 conflicts
0x8525d5a7…df09
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x18cf84a64e…8b09e4
Audit this contract →
← previous block·next block →recent activity