← previous blocknext block →recent activity
Analyzing
Block #104,033,636
16 transactions · 16 stateful · 2026-09-12 00:05:24 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,033,636 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf30c163…0fb6
0x34b655…2a6f
12 touches
15 conflicts
0xa71f18e1…6bb6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x6be58ee5…4502
0x34b655…2a6f
6 touches
3 conflicts
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0xe4164cf3…34d2
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
15 conflicts on slot 0xaf30c16357…c70fb6
Audit this contract →
← previous block·next block →recent activity