← previous blocknext block →recent activity
Analyzing
Block #104,033,123
9 transactions · 9 stateful · 2026-09-12 00:02:47 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,033,123 · 9 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
4w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x051f657c…809d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x16bce9e4…bdec
0x34b655…2a6f
2 touches
0 conflicts
0x1cab878b…5612
0x34b655…2a6f
2 touches
0 conflicts
0x28c4fba4…7071
0x34b655…2a6f
2 touches
0 conflicts
0x49299fcf…c552
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
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 0x051f657c93…33809d
Audit this contract →
← previous block·next block →recent activity