← previous blocknext block →recent activity
Analyzing
Block #104,166,978
17 transactions · 17 stateful · 2026-09-12 11:23:55 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,166,978 · 17 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
1w02w14w28w39w410w511w613w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2869417…b1cb
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1bb56de3…732e
0x34b655…2a6f
8 touches
6 conflicts
0xcea40325…6b39
0x34b655…2a6f
6 touches
3 conflicts
0xaf8ae177…8885
0x34b655…2a6f
6 touches
3 conflicts
0x483c2974…bee4
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
21 conflicts on slot 0xa2869417b8…7bb1cb
Audit this contract →
← previous block·next block →recent activity