← previous blocknext block →recent activity
Analyzing
Block #104,033,058
21 transactions · 18 stateful · 2026-09-12 00:02:27 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,033,058 · 21 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
2w03w114w016w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2a5499c6…0abf
0xa6afd3…d132
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 conflicts
0xdb067026…9eb8
0x34ae4d…3fc5
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 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity