← previous blocknext block →recent activity
Analyzing
Block #103,210,303
17 transactions · 15 stateful · 2026-09-09 02:50:00 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,210,303 · 17 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
1w03w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36aa792c…a68d
0x34b655…2a6f
4 touches
1 conflict
0x4b84a880…6abb
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x9cfd2839…96e2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0877d74b…1730
0x34b655…2a6f
2 touches
0 conflicts
0x0fb116d3…6486
0x34b655…2a6f
2 touches
0 conflicts
0x114a5de1…8b7f
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 0x36aa792c6a…6da68d
Audit this contract →
← previous block·next block →recent activity