← previous blocknext block →recent activity
Analyzing
Block #104,193,678
20 transactions · 17 stateful · 2026-09-12 13:39:14 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,193,678 · 20 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
3w05w110w011w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2869417…b1cb
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7aa5d2c4…d6ef
0x34b655…2a6f
6 touches
3 conflicts
0x8f1b3f9a…d537
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
6 touches
3 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
6 touches
3 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xa2869417b8…7bb1cb
Audit this contract →
← previous block·next block →recent activity