← previous blocknext block →recent activity
Analyzing
Block #104,032,766
16 transactions · 16 stateful · 2026-09-12 00:00:58 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,032,766 · 16 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
3w04w15w28w39w412w213w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf30c163…0fb6
0x34b655…2a6f
10 touches
10 conflicts
0x4723c2e4…45fa
0x34b655…2a6f
6 touches
3 conflicts
0x44ab25fb…e044
0x34b655…2a6f
6 touches
3 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x21844058…bc4a
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
10 conflicts on slot 0xaf30c16357…c70fb6
Audit this contract →
← previous block·next block →recent activity