← previous blocknext block →recent activity
Analyzing
Block #103,039,970
17 transactions · 17 stateful · 2026-09-08 12:31:16 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,039,970 · 17 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
2w05w08w110w211w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x31d6daa0…9313
0x34b655…2a6f
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0x82d396a1…2adb
0x91b81b…6d56
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 0x67a56c8b2e…d7f955
Audit this contract →
← previous block·next block →recent activity