← previous blocknext block →recent activity
Analyzing
Block #104,033,178
13 transactions · 13 stateful · 2026-09-12 00:03:04 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,033,178 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w28w110w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa016f004…df70
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x2531b293…51c6
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
6 conflicts on slot 0xa016f004ee…ccdf70
Audit this contract →
← previous block·next block →recent activity